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

externals usage (or alternative)

From: Andrew Sasak <andrew.sasak_at_gmail.com>
Date: Fri, 6 Jun 2008 19:04:51 -0400

We have several products that share common components. Some developers work
on multiple products. Currently the components and products are checked out
into the same root directory using a batch script for each product (so that
regardless of the number of products, each component is only checked out
once). Another batch script is used to update all of the components I was
thinking using externals would be an improvement over using the batch
scripts. However, doing this would eliminate the efficiency of having only a
single working copy for each component (because a) "The relative target
subdirectories of externals definitions *must not* already exist on your or
other users' systems", b) "the local subdirectory part of the definition
cannot contain .. parent directory indicators (such as ../../skins/myskin)."
I don't see any way to improve our current m.o., either with or without
externals. I'm sure there are plenty of others with a similar setup, how do
you handle this?
Received on 2008-06-07 01:05:15 CEST

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.