Re: [PATCH] Additions to INSTALL

Hi, Ben!

> > I'm just starting using Subversion, and this patch adds pieces that were
> > not immediately obvious for me when I tried to install the server.
>
> Hey, it's Pavel! Aren't you a famous CVS guy? :-)

Not really famous, but my name can be found in the CVS changelogs (mostly
petty things).

> Glad to see you.
>
> > + Add this line after the last LoadModule directive:
> > +
> > + LoadModule dav_fs_module modules/mod_dav_fs.so
> > +
>
> Huh? Why would we need the mod_dav_fs backend to mod_dav?

I'm sorry. I meant this line:

LoadModule dav_svn_module modules/mod_dav_svn.so

It doesn't work otherwise:

# service httpd2 start
Starting httpd2: Syntax error on line 1075 of
/usr/local/apache2/conf/httpd.conf:
Unknown DAV provider: svn

I took this line from packages/rpm/subversion.conf in the Subversion
repository. That's the only file where modules/mod_dav_svn.so is
mentioned. I would think that INSTALL should have it too.

> > + Initialize the repository. This is described in the README file.
> > +
>
> Um, at the top of section C, we have:

You are right.

> > Fire up apache 2.0:
> >
> > $ /usr/local/apache2/bin/apachectl stop
> > $ /usr/local/apache2/bin/apachectl start
> >
> > + On Red Hat, you might need to use following commands instead:
> > +
> > + $ service httpd2 stop
> > + $ service httpd2 start
>
> Ah, this seems nice... but this whole document assumes you're building
> apache2 from source code, and installing into some prefix. How does
> the redhat 'service' program know where to find your freshly built and
> installed httpd-2.0?

I see. I installed RPM files and then recompiled the latest subversion
only. The RPM files don't include apachectl, and that seem to be an
intentional decision.

From apache.spec (apache-2.0.41-0.1.src.rpm):

# remove apachectl; we have our own SYSV init stuff
rm -f $RPM_BUILD_ROOT/%{apache_dir}/bin/apachectl
rm -f $RPM_BUILD_ROOT/%{apache_dir}/man/man8/apachectl.8

Well, it took me some time to figure out how to install the server, and I
tried to help others, but obviously I should have been more careful.
Sorry for your time.

I'm still undecided whether to move some of my projects to Subversion. I
miss a command to clean up everything and return the working directory to
the original state. Compiling from a "reused" directory feels like eating
from a "reused" plate.

I wrote some scripts for CVS (known as CVS Utilities), that can do this
and some other things, and I'll have to port them to Subversion before I
can feel comfortable with it.

Subversion is a great project, and I wish I had time to help it, but there
are other things waiting for my attention, and I cannot spend more than 24
hours a day on free software :-)

Oh, by the way, you might want to add this to the "list of inconveniences"
(unless I'm wrong again):

Executable bit is ignored on import

To make files executable, use "svn propset svn:executable on FILE" for
every executable file. Then run "svn commit" to commit your changes.
"svn import" doesn't do it automatically yet.

-- 
Regards,
Pavel Roskin
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org