On Wed, Feb 06, 2002 at 02:05:04AM -0800, Tom Lord wrote:
> * What's a Revision Library?
> quickly, etc. While, officially, I hate to admit it -- I'd bet that
> revision libraries are a feature that could be easily added to
Yes, it sounds like it could be done. With a bit of scripting, I could
probably create a Python script that generate a (SVN-based) revision
But until that happens, you get to claim the feature :-)
> * Isn't Zack really neurotic about shell scripts?
hehe... It is certainly an interesting approach, and (empirically) can do
the job; I don't have any direct/immediate problem with it. However, I
believe its one serious disadvantage is integration with applications. To
create clients, custom tools, etc, those programs will need to spawn arch
tools and talk via a pipe. Obviously doable, but I prefer linking to
libraries and staying in a single process space.
(there are obviously problem spaces where scripting arch is quite
appropriate, but (IMO) things like GUIs would generally want linkage)
> * What do you *really* think, Tom?
> One problem that I perceive in the design of Subversion is that,
> very late in the game, you're wondering about the semantics of
> branches and merging -- by contrast, arch starts from clear answers
> to those questions, then asks "how do you package this into a usable
Euh... I think we aren't worried about the semantics. That's been quite
well-defined for a while (branches are just other directories, so merging is
just applying diffs from those paths against the working copy). We're
working through the implementation and code (re)factoring.
> Another problem is the whole question of mixed working directories.
> That goal follows from trying to emulate the CVS user interface, and
Nah. It is an artifact of central repositories. With a local repository, you
can assemble bits from multiple repositories. With central repo's, you
assemble a working copy from multiple repo's.
Greg Stein, http://www.lyra.org/
To unsubscribe, e-mail: firstname.lastname@example.org
For additional commands, e-mail: email@example.com
Received on Sat Oct 21 14:37:04 2006