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

Externals vs. other means

From: Jonathan Smith <jonsmith_at_members.limitless.org>
Date: 2003-05-15 13:01:28 CEST

I am going to redo our entire CM process at work, most likely using svn.
From my read of externals, I can do the following. Can I get a sanity
check that this makes sense.

We have one main Product. With every version, we send our working
materials (RCS repository included) to two other organizations (I
realize that sending the repository involves dumping and loading for
platform independence).

We also send the corresponding version of our test software, but not the
Product's Repository. Further, there are parts which do not distribute,
again an external to the non-distributable part comes to mind.

As I mentioned in another email, we have these output files used for
repeatability that are a total of about 80 meg. 1 in 20 changes will
change maybe 15% of the primary file of 68 meg. Strictly speaking, since
these can be generated by building the Product and running it, they should
be in revision control; however, for testing changes (ie. by developer 2
who just updated to get developer 1's work), they are critical. To avoid
bloating the Product's repository, I thought an external would be a great
way to include this, revision control it, but not bloat the repository to
keep it. Commit numbers for the listing files are irrelevant to me and
the users as the external always gets the right version from the external.

We also have other tools that have no reason to be released, but aren't
part of the testing, so I'm thinking to again make them their own
repository.

Summary so far:

Product Repository
        external to Lists Repository
Testing Repository
        external to Testing-InHouse Repository
Tools Repository

And, for those like to have their cake and eat it too,

Project Repository
external to Product Repository
external to Testing Repository
external to Tools Repository

This seems like overkill; however, certain parts of the repository are
releasable, certain parts no one would care about, and certain parts
aren't releasable.

Does this seem reasonable/is it proper understanding of the xvn's
externals?

Finally, what does a dump do across an external?

Thanks,

Jonathan Smith

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Thu May 15 12:59:28 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.