gnu-arch-users
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Gnu-arch-users] is there demand for itla?


From: Robert Collins
Subject: Re: [Gnu-arch-users] is there demand for itla?
Date: Thu, 20 Nov 2003 09:38:12 +1100

On Thu, 2003-11-20 at 08:25, Clark McGrew wrote:
> TLA is a very powerful system and if Tom can capture a significant
> portion of the dump CVS mind share I think he will be on easy street. 
> Can TLA capture those users?  Time will tell, but one of the requisites
> is that it must be "as easy as" CVS.
> 
> How is TLA harder than CVS?  Consider
> 
> 1) A new user wants to get an exported package and stay up to date
> 
> CVS:
> 
> cvs login -d "blahfromwebpage" 
> cvs get -d "blahfromwebpage" "package"
> cd "package"
> cvs update
> 
> TLA
> tla my-id "special format"
> tla register-archive "foofromwebpage" "blahfromwebpage"
> tla get -A "foofromwebpage" "package"
> cd "package"
> tla update -A "foofromwebpage"
> 
> The -A can be eliminated by using "my-default-archive".

Thats overly verbose.
Getting squid, as a sample, from tla.
TLA:
tla register-archive http://www.squid-cache.org/~robertc/arch/squid
tla get address@hidden/squid--HEAD--3.0 squid
cd squid
tla update

Finito. No my-id. No, -A's. 4 lines, and arguably simpler than the CVS
ones.

> 2) A new user wants to import source
> 
> CVS: 
> 
> export CVSROOT="blah"
> cvs init
> cd new-source
> cvs import "repository" "vendor tag" "release tag"
> cd ..
> cvs get "repository"
> 
> TLA
> 
> tla my-id "special format"
> tla make-archive "archive" "location"
> tla my-default-archive "archive"
> tla archive-setup ... 
> cd new-source
> tla init-tree ... 
> tla make-log ... 
> tla import

Again, you are using uneeded extra commands. 
Here you do need my-id, but you only run it once. 
my-default-archive isn't needed. Here are the commands I used when
demoing arch to my local LUG, adapted to your example above.
$ tla make-archive address@hidden \
~/source/slugexample/repository
$ cd new-source
$ tla init-tree address@hidden/example--mainline--1.0
$ tla id-tagging-method tagline
$ tla import -s


> 3) A user wants to connect to an existing project using ssh
> 
> CVS:
> 
> export CVSROOT="blah"
> cvs get "stuff"
> 
> TLA:
> 
> tla register-archive "archive" "location"
> tla my-default-archive "archive"
> tla get "stuff"

Huh? 
$ tla register-archive "location"
$ tla get "stuff"

> 4) A user wants to commit
> 
> CVS:
> cvs commit
> 
> TLA:
> tla make-log
> edit <log-file>
> tla commit

Huh?
tla commit -s "blah blah blah"

You are making tla much harder for yourself that it needs to be. itla is
a nifty concept as I've already said: but don't justify your support on
the basis of using tla in a difficult fashion.

Rob
-- 
GPG key available at: <http://www.robertcollins.net/keys.txt>.

Attachment: signature.asc
Description: This is a digitally signed message part


reply via email to

[Prev in Thread] Current Thread [Next in Thread]