[Bese-devel] configs suggestion

Chris Capel chris at iBankTech.NET
Wed Nov 24 15:31:27 UTC 2004


I hate outlook.

"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.

Marco Baringer <mb at bese.it> writes: 
> 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.

Not so much "lose" as have to get libraries manually or mess with the
config file. I copied over the dev config from the support--dists and
modified it for to be used with a tagged ucw--dev.

So yeah.

You know what, though? 'tla buildconfig' should support a --tag option
of some sort. Someone should go bug Tom Lord. Or I should get busy on a
CL tla clone. :-)

Chris Capel

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://mailman.common-lisp.net/pipermail/bese-devel/attachments/20041124/b11ff281/attachment.html>


More information about the bese-devel mailing list