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

Re: Recommended build method for SVN?

From: Ben Collins-Sussman <sussman_at_red-bean.com>
Date: Sun, 30 Nov 2008 22:30:26 -0600

Do you really need to be rebuilding svn trunk code daily, in order for
your own project to make progress? If not, why not just have *one*
person (you?) build trunk every month or so, and distribute the
libraries via svn.

I can't believe I'm recommending this, since I've spent years telling
people to only put 'non-derivable' stuff (i.e. code) into version
control... but building svn on Windows is Really Really Hard.

On Sun, Nov 30, 2008 at 10:18 PM, Robert Dailey <rcdailey_at_gmail.com> wrote:
> Hi,
> I'm creating my own open source project that will utilize the Subversion
> API. However, I want to minimize the amount of dependency building I have to
> do on various platforms, specifically Windows since it is the most difficult
> to deal with. I want to directly use the code from the subversion
> development trunk, however I'm not sure what the best way to go about that
> is. My main concern is the APR and Neon libraries, as well as any other
> mandatory dependencies Subversion has. How do you guys recommend handling
> these dependencies? I would prefer to have all third party source code in my
> repository for my project to make checkouts quick and simple. I want to
> avoid forcing people to go out and hunt down libraries and compile them,
> especially on Windows, since this could literally take hours.
> Thanks for reading.

To unsubscribe, e-mail: dev-unsubscribe_at_subversion.tigris.org
For additional commands, e-mail: dev-help_at_subversion.tigris.org
Received on 2008-12-01 05:30:37 CET

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

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