From: Victor A. Wagner, Jr. (vawjr_at_[hidden])
Date: 2003-08-27 23:54:27
When I first saw the suggestion that I got a tarball, I wrote a very
snappy, angry, and not very humorous piece about not being a eunuch (a
name I decided to apply to a *nix user, it being what appears to be an
acceptable spelling of the singular of unix (at least if you pronounce it
in American English, my milk tongue)).
I have NO idea what a tarball is, other than *NIX people seem to go gaga
I don't know if I have any tools that would reliably deal with one, and I
don't really have time to find out.
The almost implicit assumption that if you're a "real programmer" you've
got to understand all this gobbledegook from the *nix world simply isn't
true. I've GOT CVS, and I use it, THAT is a tool that we all have (or
could trivially) and it's _supposed_ to be the "official repository" of the
You're right. I'm building directly from the CVS output (as noted in
another reply) once or twice a day.
what follows is OPINION
IF you want people to check the ongoing work, it behooves the "library"
developers to make it as simple as possible for us to get (and test) the work.
This means that the users should NOT have to change ANYTHING in their
testing procedure that has to do with imminent releases or any other
entirely internal (to the library (boost in this case)) conditions.
it is unacceptable that a tester may suddenly need to update -r
SOME_MAGIC_LABEL because a release branch has taken place. the main
reason is that "SOME_MAGIC_LABEL" has no meaning to the testers
they might have missed the "we're gonna release 1.30.2 next week" message
on the EMail.
I really don't see any other reasonable approach to dealing with a large
project that (in some cases) needs to be tested all together. If there is
no "anchor" for what to test, then how does one automate the testing?
At Wednesday 2003-08-27 00:51, you wrote:
>Victor A. Wagner, Jr. wrote:
> > you're stubborner than I am, and I've had a helluva lot more practice.
> > I give up.
>I'm sorry that you've given up, but I don't think it's fault of Boost.Build
>You write an email saying that M6 is plain broken. I certainly get tarball
>from SF and find that it works for me. Looking further at your email, I
>decide that the most possible cause is that you're not using tarball, but CVS
>state of boost. I also say that to use CVS state you need to rebuild bjam,
>and use "bjam --v2 --version".
>It does not seems like you've tried to install the tarball as is, and it does
>not seems like you've rebuild bjam. Maybe, you can try either approach, and
>let us know if there are problems?
>Yahoo! Groups Sponsor
>To unsubscribe from this group, send an email to:
>Your use of Yahoo! Groups is subject to the
><http://docs.yahoo.com/info/terms/>Yahoo! Terms of Service.
Victor A. Wagner Jr. http://rudbek.com
The five most dangerous words in the English language:
"There oughta be a law"
Boost-Build list run by bdawes at acm.org, david.abrahams at rcn.com, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk