From: Vladimir Prus (ghost_at_[hidden])
Date: 2003-10-09 23:51:50
Rene Rivera wrote:
> #3 is only needed if one doesn't want old tagged versions to retrieve the
> new files. That is, so that when someone does a "cvs co -rVersion_1_30_2"
> they don't get the v1 & v2 directories.
> >> For step #2 SF suggests writting a script they can execute. See the
> >> attachement for that. I'd like other people to look it over for errors.
> >I haven't seen any.
> I did... I forgot to account for files in the "Attic".
Oh... they should be copied too?
> >for all staff in "new", in my opinion. Comments are welcome.
> >boost-build.jam ??? maybe just remove
> Ultimately yes remove it. But putting it someplace first, then doing a "cvs
> remove" is safer.
> >site-config.jam build?
> >user-config.jam build?
> Since those are default configuration files, would it be best to put them
> at a more "user visible" location, like at the v2 subdir.
> >test.jam build?
> And since this one covers multiple directories it would also make sense to
> put it in the v2 subdir?
Actually, now I think it's better to move it to "test". After all it's about
running unit tests and all tests are in "test" now.
> >Besides, I have one idea: I recall SF provides CVS snapshots. We can get
> >run your script and check if the results are OK. I'm about to download it
> >now, not sure how much it will take ;-)
> Good idea... and as soon as the cvs.sf.net web server is working I'll get
> the snapshot also, at least so I can see what the Attic files are.
Yea, same problem here. I get wierd errors about some proxy or something like
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