[Bese-devel] configs suggestion

[Marco Baringer]

"Chris Capel" <chris at iBankTech.NET> writes:

> Here's the trick. In both of your examples, you don't tag the UCW
> branch. You just "get" it. That means that the archive ('tla
> tree-version')remains the one at common-lisp.net. If I want to put it in
> my local archive, I need to tag it instead. When you do a get like that,
> tla expects that you won't be wanting to edit it any time soon. There's
> lots of little differences between a get and a tag, and a tag is the
> recommended way to get a branch if you want to import it into your local
> archive. So, why doesn't your second example work? Because once you've
> gotten ucw--dev (which is what buildcfg uses to download the trees) you
> can't tag it! Well, you can tag ucw-2004/ucw--dev, but then it just goes
> out to common-lisp.net again. So you have to tag straight away, before
> you've downloaded anything. support--dists really just gets in the way
> of that. It's really just a tagging issue.

is the problem that when you tag ucw--dev you "lose" the dev configs?
(you can't use support--dists anymore)

for example, if i want to tag ucw--dev and work on stuff in my local
archive (mb-2004 at bese.it):

$ tla tag ucw-2004 at ucw--dev mb-2004 at bese.it/ucw--foo
$ tla get mb-2004 at bese.it

of course, while this gets me the ucw stuff it can't do tla buildcfg
dev and get all the support libs. hm, this is not nice.

> Granted, once you've done a 'tla get' you can do 'tla set-tree-version'
> to your local archive and 'tla add-log-version' and then 'tla import',
> but when you go and do that import, the logs get all messed up, and I
> imagine you lose the seamless border between the archives (though I'm
> not sure). So it's really not preferable.

no, that would be Bad.

-- 
-Marco
Ring the bells that still can ring.
Forget your perfect offering.
There is a crack in everything.
That's how the light gets in.
     -Leonard Cohen