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

Re: Large project architecture and similarities to Svn

From: Garrett Rooney <rooneg_at_electricjellyfish.net>
Date: 2006-03-30 22:39:48 CEST

On 3/30/06, Matt England <mengland@mengland.net> wrote:

> I'm looking for perspectives on how to manage the source for these external
> libraries. I see in the current trunk
> (<http://svn.collab.net/repos/svn/trunk/>) that there is no 'apr' nor
> 'neon' directory as documented per
> <http://subversion.tigris.org/hacking.html#directory-layout>. Are these
> vendor-external source sets still managed by Subversion? Last time I build
> svn (from a 1.3.0 tarball) I recall the src tarball including apr and neon
> software.

We include those in our release tarballs as a courtesy to users,
they're not stored in our repository, but if the directories are
present the build system will take advantage of them. In general, I
don't think most developers actually put apr/apr-util/neon there for
development purposes, personally I tend to install versions into a
special --prefix and use that for day to day development.

(This is different on windows of course, where you basically have to
have them as part of your source tree in a location dictated by the
build system.)

-garrett

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Thu Mar 30 22:40:19 2006

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.