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