| 1 |
I've attached a short log of the more recent changes I've made to my |
| 2 |
rewite branch. This includes rebasing the broken seed stage update |
| 3 |
commit with dwfreed's patch which fixes the binpkgs not being |
| 4 |
created/used in stage1. |
| 5 |
|
| 6 |
There are a few trivial commits with some of the more notable ones |
| 7 |
being: |
| 8 |
|
| 9 |
Creating and using a new AutoResume class for handling all file |
| 10 |
operations involving the "autoresume" feature. This keeps the code |
| 11 |
logic in one place, easy to maintain and change. It also removes a |
| 12 |
great deal of duplicated "if ..." checks and code which follows. |
| 13 |
|
| 14 |
Another removes a bunch of duplicated code in the ClearBase class. |
| 15 |
|
| 16 |
I have also started using snakeoil's lib functions for version |
| 17 |
generation in the live git checkouts. As well as some other of it's |
| 18 |
osutils. |
| 19 |
|
| 20 |
I've updated my rewrite with the other changes to master since I did |
| 21 |
started the rewrite branch. Some commits were just cherry-picked |
| 22 |
across, some needed minor editing to suit. A few needed the changes |
| 23 |
needed to be applied manually to the newer code. |
| 24 |
|
| 25 |
Since I did a bunch of rebasing to my original batch of commits, you |
| 26 |
will need to: |
| 27 |
|
| 28 |
"git pull --force whatever-you-named-my-remote rewrite" |
| 29 |
|
| 30 |
or for a new clone: |
| 31 |
|
| 32 |
git clone --branch rewrite http://dev.gentoo.org/~dolsen/catalyst/ |
| 33 |
|
| 34 |
|
| 35 |
As of the last commit cd733bf2bfc04659372984fe88415d18e5eb2991 |
| 36 |
everything has been working according to my testing (up to stage3 |
| 37 |
tested) |
| 38 |
|
| 39 |
Please run your tests on it to see if I've missed anything. |
| 40 |
|
| 41 |
I'll work on refactoring the compression/decompression code soon which |
| 42 |
will be another larger change. It should be just a matter of |
| 43 |
adding/removing some defaults/config options to add new capabilities. |
| 44 |
There should be no need for further code changes when it is done. Time |
| 45 |
will tell of course... |
| 46 |
|
| 47 |
There are too many commits/changes to spam this list with. For those |
| 48 |
that wish to review them individually, I suggest using dev-vcs/gitg |
| 49 |
which is a very nice gtk frontend to git. It is great for reviewing |
| 50 |
commits/changes for any of the branches. It also has the ability to let |
| 51 |
you hand pick individual changes from a displayed diff for generating |
| 52 |
commits. |
| 53 |
|
| 54 |
Once there is a rewrite branch in the main repo, you will be able to |
| 55 |
view changes in gitweb without the need to download them. |
| 56 |
-- |
| 57 |
Brian Dolbec <dolsen@g.o> |
Archives