1 |
I've cherry-picked the recent repoman changes for the new git tree onto |
2 |
a new branch starting at the 2.2.20 release. This should take care of |
3 |
all the recent flood of emails about the new workflow. I also included |
4 |
a few man page corrections and improvements. |
5 |
|
6 |
|
7 |
Future: |
8 |
|
9 |
I hope to get the repoman rewrite changes merged into the master branch |
10 |
within about a week. Although I have not completed what I considered to |
11 |
be a completed stage1 process, it is very close to my original target. |
12 |
|
13 |
At that time I will make a portage-2.2.21 release. It has additional |
14 |
emerge/portage bugfixes. I will warn you that the repoman rewrite code |
15 |
is bound to have some regressions. I am seriously considering including |
16 |
the original repoman code so devs are not stuck re-emerging a different |
17 |
portage version if they find a bug blocking them from using it. But I |
18 |
do want it to get a much broader testing base. |
19 |
|
20 |
So, please consider older repoman code to now be frozen. Any more |
21 |
repoman changes should be based on the repoman branch of the portage |
22 |
repo. If it is something that absolutely needs to be applied to |
23 |
2.2.20.1 as well, then please submit 2 patches, 1 for each branch. |
24 |
There can be potentially a great deal of rebase errors to fix while |
25 |
attempting to rebase the rewrite on a changing master's code. |
26 |
|
27 |
For those of you willing to test the repoman branch code to flush out |
28 |
as many bugs/regressions as possible before it is merged into master. |
29 |
I thank you in advance. The new repoman code can be run from the |
30 |
checkout without being installed. What I did was create a symlink in |
31 |
my users bin/ directory pointing to the checkout's bin/repoman with a |
32 |
slightly different name. That way you can compare the installed |
33 |
repoman's output with the rewrites. Be aware there can be some slight |
34 |
differences in formatting, but the data should be the same. |
35 |
|
36 |
Thank you... |
37 |
-- |
38 |
Brian Dolbec <dolsen> |