On Sun, 2005-02-27 at 23:02 -0500, Jeffrey Creem wrote:
> We currently use an IDE with a built in version control system (Rational
> Apex). Note that though this is a Rational (IBM now) tool it is not
> built on Clearcase.
> While there are many things that SVN has that Apex does not, there
> appears to be at least one important (to me) feature that I do not see
> any good way simulate with SVN.
> The basic idea (in SVN terms I think) is that Apex allows one to create
> branches where most of the files are not really branches at all but are
> still connected to the trunk. This can be used for lots of things. We
> use it to handle
We were speaking about being able to do at some recent point on IRC.
In particular, being able to auto-update to newer revisions of
"unmodified on branch files".
This is somewhat different than keeping a copy-history, because you just
want to say "Use this revision for this file, from now on", since it
Unfortunately, even this requires schema changes to the repository
schema (you need to add something to the nodes in a given revision to
let them be shared with some other node, but have a different
predecessor id), so it can't happen until 2.0.
> 1) A large common code base that serves all customers but where a very
> small number of files need to be forever branched to support different
> 2) Sort of a version control system "preprocessor" approach where
> certain files need different contents based on the target platform (e.g.
> an embedded OS v.s. a host OS).
> I don't see any way of getting similar functionality or workflow in SVN
> without lots of branching/merging to keep the "common" files in sync.
For now, you could probably "abuse" svn:externals to do this if you can
keep the branched files in a seperate directory (svn:externals lets you
point at directories, not files)
To unsubscribe, e-mail: email@example.com
For additional commands, e-mail: firstname.lastname@example.org
Received on Mon Feb 28 06:03:40 2005