2009/2/12 Peter W. Draper <[log in to unmask]>:
>
> As part of the move to git, we need to move most of the packages out of
> the thirdparty tree and into their own repositories. This is so that we
> can continue to track the code changes from the originator releases
> easily.
>
> (Each of these new repositories, created lovingly by Tim, has two
> branches, master and vendor. The master branch is our patched version of
> the package and vendor tracks the actual releases from the thirdparties.
> New releases are added to the vendor branch and merged into the master.)
>
> Each of the moved packages will be added back into the thirdparty tree as
> git submodules. That shouldn't be much of a problem except that getting
> the initial downloads and subsequent updates takes some manual
> intervention as these do not update using a normal pull.
>
> To make this easy I've added a new script to the toplevel called
> "update-modules". If you run this all the submodules be checked out, if
> needed, and brought up-to-date. This is also ran by the toplevel
> bootstrap, so you don't need to do this for fresh checkouts. However, as
> each thirdparty submodule appears you will need to run this script and
> rebuild the package in your existing working trees.
>
> For a start I've just finished adding the MATCH package, so after your
> next pull the current match-0.8 directory should be deleted and replaced
> by an empty match directory.
Hmm... Now that jac is back on the air, I've done a "git pull
--rebase", but the thirdparty/rit/match/match-0.8 directory in my
checkout still has stuff in it.
> To complete this update you'll need to run
>
> % ./update-modules
> % cd thirdparty/rit/match
> % ./bootstrap && ./configure && make && make install.
So do I go on with these commands or not?
David
|