[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: Mac OS X - best setup for small developer?

From: Aaron Hilton <otri_at_uvic.ca>
Date: 2005-03-24 18:56:10 CET

On 23-Mar-05, at 8:53 PM, Dave Camp wrote:

> On Mar 23, 2005, at 2:40 PM, Craig Heilman wrote:
>> (2) Any benefits in my situation to using svnserve or mod_dav_svn
>> under Apache rather than local access?
> That requires Apache 2.0 (unless I'm mistaken) and Mac OS X client
> ships with Apache 1.x. You would have to manually install Apache 2.0
> alongside the existing Apache. I've seen instructions on the net for
> this but I've not tried it myself.

I have configured Apache 2 under Mac OS X with relative ease using
Fink. The real benefit of accessing your repository through the web
server is the ability to log in from anywhere and browse the contents
of your repository. Then you can pull word or pdf documents for your
client at times when you're caught without your laptop. You can also
grant your client access to the repository without being forced to
create a whole unix account under Mac OS X.

Details here:

I would instal Fink, then using that, install the apache 2 web server
and SVN packages. The apache 2 configuration will co-exist with the
default Mac OS X Client Apache 1.3 server.

It's good you chose FSFS because I had corruption, hanging, and other
problems while using BDB. Once I converted over to FSFS there have
been no further issues. Note, the hanging may have been from the
particular version of Apache 2 I had installed, so I would recommend
getting the very latest release of apache under the "unstable" branch
under fink. You will have to modify /sw/etc/fink.conf to do this.

If you have any questions, feel free to ask.
- Aaron.

To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Thu Mar 24 18:59:01 2005

This is an archived mail posted to the Subversion Users mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.