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

best practices for nested externals

From: Brian Marshall <mimarsh2_at_gmail.com>
Date: Mon, 5 Jan 2009 11:51:00 -0500

I am a long time SVN user, but rather new to setting up repository
structures and administration.

Here's my situation. I have a core library and a math library that
depends on the core library. Many products need both libraries. What
is the best way to handle this? Math has core as an external. When
Product brings in Math that in turn brings in core. Product also
needs to reference core files, but I don't like having the same core
files in 2 places. For example the product has externals core and
math, and math has core as an external.

Is there a better way to do this?



To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_subversion.tigris.org].
Received on 2009-01-05 20:15:14 CET

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.