Hello All,
I was dissappointed when we decided to remove images from the main
gjallar repository, so I have been seeking a solution.
For managing gjallar images with mercurial I have attempted to use
mecurial queues but this was not really workable. Instead I have been
successfully using nested repositories.
To set this up,
You clone the main repository as usual.
so the gjallar/.hg directory is the repository.
Then in the dist directory where you are typically working you
initialize a second repository.
hg init
then you
hg add Gjallar0.4.image
hg add Gjallar0.4.changes
hg commit
these are added and committed to the new inner gjallar/dist/.hg repository!
So when you want to make changes to the outer repository just cd .. ,
into the outer gjallar directory and make your changes
adds/updates/commits/push/pulls from there
This scheme theoretically allows you to commit a snapshot of your image
and also the database state if you add that as well. You can of course
return to any previous snapshotted state, and I dont think it uses as
much disk as having lots of images as per my usual practice. Its great!
Keith
_______________________________________________
Setools mailing list
Setools@lists.squeakfoundation.org
http://lists.squeakfoundation.org/mailman/listinfo/setools
