Mailing-List: contact dev-help@brooklyn.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@brooklyn.apache.org
MIME-Version: 1.0
Date: Sat, 5 Dec 2015 23:46:10 +0000
Message-ID: 
 <CABQFKi23w96TrguxWh8Kk9DC163FqKVxxoNt7ebhQpE-qquAbw@mail.gmail.com>
Subject: Repository splitting script
From: Richard Downer <richard@apache.org>
To: Brooklyn dev <dev@brooklyn.apache.org>
Content-Type: text/plain; charset=UTF-8

All,

Per the recent vote on this list, we have decided to split the
Brooklyn repository into a number of smaller modules.

With some of my colleagues, I've been working on a script to do this,
which preserves as much of the existing history, branches and tags as
possible.

You can find the script here:
https://github.com/rdowner/brooklyn-repo-split/tree/master

And the result of running the script:
https://github.com/rdowner/TEMP-brooklyn-dist
https://github.com/rdowner/TEMP-brooklyn-docs
https://github.com/rdowner/TEMP-brooklyn-library
https://github.com/rdowner/TEMP-brooklyn-server
https://github.com/rdowner/TEMP-brooklyn-ui

I'd be interested in your feedback!

--

One limitation of this script occurs when files are moved between
locations that turn into different repositories after the split. My
expectation is that files would suddenly appear in the new repository
without history.

Alex Heneveld has suggested a pre-processing phase which examines all
the files currently in each proposed subrepo, and then examines the
history to determine every filename that they have previously been
known as, and uses that in the whitelist for selecting the contents of
each subrepo. This would preserve history (although the subrepo
history would look a bit odd, as the early history of the repo would
have isolated files in random locations).

I haven't implemented Alex's suggestion, but the design of this script
would easily allow the results of the pre-processing phase to be
integrated.


Cheers
Richard.