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

Re: use svn:externals for build/generator/ezt.py?

From: C. Michael Pilato <cmpilato_at_collab.net>
Date: 2003-10-31 15:40:59 CET

Thom May <thom@planetarytramp.net> writes:

> * Russell Yanofsky (rey4@columbia.edu) wrote :
> > Garrett Rooney wrote:
> > > ...
> > >> If using svn:externals for APR would give subversion it's own private
> > >> copy
> > >> of the library, is this desireable? I've just been using the APR that
> > >> comes
> > >> with apache...
> > >
> > > It'd certainly be nice, if APR used Subversion ;-)
> >
> > What would be nicer about having two copies of the same library?
> >
> Eh?
> APR (and the rest of Apache) eventually (or not so eventually) want to move
> to SVN. At that point, we could just svn:externals the real repos. No-one is
> talking about having two copies.

Whoa, folks. T

he point I think Russell is trying to make is that svn:externals
aren't an option for processing. If you checkout subversion and there
is an svn:externals set on the trunk directory that sez "Oh! Go get
APR" then everyone who checks our Subversion gets APR. But there are
folks (like Russell and myself, and surely others) who don't *want*
APR in our Subversion trees, because we build against the APR that is
installed with our Apaches. To fetch APR would be to produce a second
copy of that code on our disks -- the first living under

As for the "eating our own dog food" stuff -- that's probably useful
in situations where we someday expect that food to be tasty. But
Subversion's svn:externals is more like dog *poo*, not recommended for

To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Fri Oct 31 15:42:15 2003

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.