tools/build restructuring

From: Rene Rivera (grafik666_at_[hidden])
Date: 2003-10-08 18:42:28

Some time ago we talked about restructuring the Boost.Build code so that it
would easier for everyone to work and use v1 and v2. The goal was to move
the code for each into subdirectories tools/build/v1 and tools/build/v2. I
did some reading of CVS and the easiest, safest, and least disruptive way is
to use the "copy history files" method. The steps involved are:

1. Creating the new location directories, v1 & v2 in our case.
2. Copying the *,v CVS history files to the new locations. This involves
direct manipulation of the CVS repository so the SF staff has to do this
part.
3. After getting the new structure... Deleting non-branch tags from the
new files.
4. Making any changes to make the new structure work.
5. Removing the now duplicated old files.

The major advantage of that above is that the old structure is still
available to users while we make any fixes to the new structure. Another is
that we keep all the history, the old files are there and retrievable
(doesn't break previous versions), and the new files still have the complete
history (but don't show for old versions).

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. And
I have one structural question... Since we are talking about moving
basically all files around, would now be a good time to also move the v2
files in the "new" subdir to their "correct" locations? And if so, what are
those new locations?

-- grafik - Don't Assume Anything
-- rrivera (at) acm.org - grafik (at) redshift-software.com
-- 102708583 (at) icq --21384773-2295726080-3274627350=:9001 Content-Type: application/octet-stream; Name="boost-build-restructure.sh"; X-Mac-Type="54455854"; X-Mac-Creator="522A6368"
Content-Transfer-Encoding: base64
Content-Disposition: attachment; Filename="boost-build-restructure.sh"

[Attachment content not displayed.] --21384773-2295726080-3274627350=:9001--