[openbeos-build-team] Migration
- From: "Erik Jaesler" <erik@xxxxxxxxxxxxxx>
- To: "OpenBeOS Admin" <obos-admin@xxxxxxxxxxxx>,"OpenBeOS Build Team" <openbeos-build-team@xxxxxxxxxxxxx>
- Date: Thu, 04 Jul 2002 13:02:34 -0700
My apologies first for the amount of time this is taking (I know
everybody has basically been waiting for this move since January) and
second for the overlap that will happen by hitting both the admin and
build team lists.
I am releasing the migration scripts as "alpha"; you can get them at:
http://www.cgsoftware.com/erik/migrate
migrate is still a bit messy, but has the nifty feature that you can
specify what you want to move. For instance, to migrate the storage
kit:
migrate storage_kit
Multiple targets can be specified. You can do 'migrate help' for a list
of all the targets.
The second script, renew, is quite valuable for testing. Basically, it
will remove directories from 'current' and get fresh copies (from the
dir specified in RENEW_DIR) to repopulate the old tree. This requires
having another copy of the source tree handy, which brings me to an
important point:
PLEASE, PLEASE, PLEASE!!! make a copy of the source tree and do all
testing there. You can use your original directory as the source for
renew operations (just set RENEW_DIR to point there). I'm paranoid
enough that I have *3* copies of the tree: my working copy, my renew
copy and my migration test copy.
renew is also targetable and handles multiple targets. If you're
specifying a target, just remember to include 'current' -- things can
get a bit weird if you don't remove that directory before doing a new
migration (time allowing, I will make current an implicite target). As
with migrate, renewing the storage kit looks like this:
renew storage_kit current
Both migrate and renew will default to all targets if none are
specified.
Each team lead please test the migration of your module -- make sure
everything gets moved where it should. Let me know if there are *any*
issues.
As an aside, if the build team is looking for something to do while
waiting on the migration, I would like to respectfully suggest that they
go through the tree and convert everything that is currently using a
makefile or BeIDE project file to use a Jamfile. migrate is currently
set up to move Jamfiles, but not makefiles or BeIDE project files -- to
help encourage conversion, of course. =)
Thanks, and good luck.
e (who hopes everybody remembers this is *ALPHA* ;)
PS: if you migrate the kernel_kit target, you will need to renew current
and openbeos -- there is no kernel kit target for renew.
Necessity is the plea for every infringement of human freedom. It is the
argument of tyrants; it is the creed of slaves.
-William Pitt, British prime-minister (1759-1806)
Other related posts:
