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

Re: let's kill svn:externals

From: Garrett Rooney <rooneg_at_electricjellyfish.net>
Date: 2003-07-23 18:39:12 CEST

Régis Priqueler wrote:

> I need it. And i think if you programming object code or php you need it.
> Or another simple way to use it.

I don't see how this is any different from any system where you get
source code from different places. Set up a local script to check out
the various different parts of your tree and you're all set. This just
doesn't seem like the kind of thing your version control needs to automate.

> I had always used modules with generic library used by several
> projects at once but not with the same version.
> Now i'm working with php and i'm using modules for the common objects
> (database access...) used by my sites.
> So the svn:externals is a good idea. I'm new in the SVN world and maybe
> there is other way around to achieve the same functionality.
> The only real drawback i see is that export didn't seem to care about
> it.

The problem is that export is just one of the many things that end up
not working with svn:externals.

> But if you give me a workaround as simple i take it ;-)

A workaround for export not respecting externals? Use checkout instead,
it does. A workaround for not having externals? Include in whatever
build scripts your project has the commands to check out the various
different parts of your tree that you need.


To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Wed Jul 23 18:40:07 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.