[Gnu-arch-users] Re: [MERGE REQUEST] changeset translation preparatory work

[Greek0]

On Sun, 30 May 2004 10:45:49 -0400
Colin Walters <address@hidden> wrote:

> On Sun, 2004-05-30 at 07:01, address@hidden wrote:
> 
> > You miss one major point. It's been mentioned by Miles already. What
> > about compatibility with other apps and wrappers around tla? Some
> > functions will break if {arch} doesn't exist any more.
> 
> My growing feeling about this is that if any apps or wrappers do, they
> are buggy.  You want to find the tree root?  Use "tla tree-root". 
> Want to find out the tagging method?  "tla tagging-method".  See all
> the patch logs? "tla logs --merges".

All of these being butt slow :-/

> > How should it be customizeable? Should the dir name be compiled into
> > tla? 
> 
> I think it will be say ~/.arch-params/default-project-tree-version.
> 
> > With per-user you get the problem that user A
> > migth not be able to do anything on a wd of user B, if their
> > dir-names differ. He can't even do a simple tla changes or anything
> > like that. It might still be the best option though.
> 
> Yes.  But I think the case of two users who are using different
> versions of tla but sharing a working directory would be quite
> uncommon, if it would ever really happen.

They don't need to use different tla versions, but only different
arch-meta-data dir names.
I admit it might not be very common, but I'd expect tla to work smoothly
on a wd that another user checked out. I probably won't commit, but at
least changes, ... should work.

Please don't get me wrong, I don't think it's a bad idea to use .arch as
meta-data-dir, but I think it's problematic to do it now. I'd like to
see it together with all the other incompatible changes that would be
nice to have in tla, ie. archive format changes.

Cheers,
Greek0