Re: Killing bitkeeper history

Andy Chittenden wrote:
> I hope I haven't misunderstood what's trying to be achieved but here's
> what we do with tar balls.
> 
[... cut long description ...]

 From what I understand from quickly reading this description; is
that you are bookkeeping changesets against the actual contents
of the dist tarball and then applying these changesets to
the latest compatable release as they come out... it sounds like
a really great setup.

What we are using is alot less elaborate; when we modify a
third party it looks kind of like this:

===================================
$ tar -zxf thirdparty_repo/package.tgz
$ cd package
... code patch and document changes ...
$ make
... and here comes the cute part ...
$ rm -rf distrib
$ make DESTDIR=`pwd`/distrib install
$ make clean
$ tar -zcf ... recreate tarball
===================================

Its really simple and stupid... at least it lets us
loop over the repository and recreate a full OS with
third-party libs with little or no problems.

Unfortunately its not the time to go re-inventing the wheel,
so troubleshooting will look mostly like removing and copying
trees across repositories etc or temporarily working without
history (ewww).

Cheers and thanks for your input ;-)
                        -Tristan

-- 
A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
A: Top-posting.
Q: What is the most annoying thing on usenet and in e-mail?