You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@subversion.apache.org by Steve Cohen <sc...@javactivity.org> on 2005/02/01 01:51:08 UTC

Re: Is subversion ready for primetime

Max Bowsher wrote:
> Joseph Silverman wrote:
> 
> 
>> Trying to find rpm's for not-latest version of linux for Apache, and
>> all it's modules, has been rather impossible, in fact.  So I have
>> resorted to a "barebones" Apache server which is ONLY used by svn
>> (simplifying this somewhat and allowing me to proceed).
> 
> 
> Of course, using a current-ish distro would also have been a non-painful 
> way to go.
> 

What's "currentish"?

Using RedHat 9.0, I went through hours of hell trying to get my 
subversion to work right.  Following the instructions (using --nodeps is 
a really BAD idea),  I wound up disabling my apache server. 
Fortunately, I wasn't using it for anything, until I wanted to try with 
subversion again.  I had two or three go-rounds of "uninstall apache and 
all in its dependency chain, then reinstall" before I got it right.  The 
instructions are NOT clear enough.  This, I suppose, might be part of 
what Joseph meant by "ready for primetime".

Of course the blame for this falls partially on RedHat with its 
bifurcation into "enterprise" and "hobbyist" lines.  When there was only 
one, it seems to me there was more support for the "hobbyists".  But I 
suppose they have to make a profit.  I'm not sure which way I want to 
head in going forward and it's only going to get worse.  But I didn't 
feel like upgrading to Fedora just to install Subversion at the present 
time.

In case anyone wants to pursue improving the documentation, here are 
some clues.  With RedHat 9.0, there are 17 rpms that fall under the 
"Webserver" category in its installer.  When I installed RH 9.0 I had 
said "install everything".  After my uninstall-reinstall, I only 
reinstalled 12 of the 17, the "default" configuration of the category. 
I had no need of the other five.  Then and only then was it possible to 
get beyond a broken Apache and install Subversion.  The instructions may 
have assumed the default configuration - but they don't say one way or 
the other.

On the plus side, though, I will say that it is, finally, POSSIBLE to 
install Subversion.  Ultimately, I succeeded and it seems to work well 
enough.  Keep at it Joseph, you will get there.


Steve Cohen

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org

Re: Is subversion ready for primetime

Posted by Steve Cohen <sc...@javactivity.org>.
Igmar Palsenberg wrote:
>>What's "currentish"?
>>
>>Using RedHat 9.0, I went through hours of hell trying to get my 
>>subversion to work right.  Following the instructions (using --nodeps is 
>>a really BAD idea),  I wound up disabling my apache server. 
> 
> 
> Best thing to do is setup a seperate RPM for svn use only. Since svn 
> requires recent db version linked in, I don't like the idea of a system 
> upgrade screwring up svn.
> 
> If anyone is interested, I could cook up an svn + apache 2 RPM that can be 
> used with touching the original apache installs.
> 
> 
> 
> 	Igmar
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
> For additional commands, e-mail: users-help@subversion.tigris.org
> 
> 
> 
That sounds like a great idea.

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org

Re: Is subversion ready for primetime

Posted by Igmar Palsenberg <ma...@jdimedia.nl>.
> What's "currentish"?
> 
> Using RedHat 9.0, I went through hours of hell trying to get my 
> subversion to work right.  Following the instructions (using --nodeps is 
> a really BAD idea),  I wound up disabling my apache server. 

Best thing to do is setup a seperate RPM for svn use only. Since svn 
requires recent db version linked in, I don't like the idea of a system 
upgrade screwring up svn.

If anyone is interested, I could cook up an svn + apache 2 RPM that can be 
used with touching the original apache installs.



	Igmar

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org