May be good to change 'revision' type in ebuild name theme from -r# (where '#' is integer) to -r#C (where 'C' is string) or add next field 'brand' (-r5cool.ebuild or -r5.cool.ebuild) Now I can't mark some ebuild as 'my' and if I do 'emerge -pu' I can't see which "my" ebuild are updated. In RedHat, Mandrake, Debian this problem don't exist. I always can to name package as qqq-1.0-12spm.deb or qqq-1.0-12mdk.rpm Of course, qqq-1.0-r1my.ebuild (or qqq-1.0-r1.my.ebuild) must be newer than qqq-1.0-r1.ebuild, but older than qqq-1.0-r2.ebuild Reproducible: Always Steps to Reproduce:
Created attachment 18495 [details, diff] untested patch This is a highly untested patch to implement a vendor tag after the release number. It might break portage completely, so a backup is handy.
Created attachment 18516 [details, diff] updated patch this patch fixes the 9>10 bug from the previous patch
Created attachment 18921 [details, diff] updated patch fixed a problem with ~ dependencies
Test this in catalyst or some other vigourus way.
Marius, did your version handling rewrite in some way address this (don't have the regex in front of me atm).
nope, IIRC I had some issues (collate sequence being one) with this and didn't really track it anymore.
Putting a hold on feature requests for portage as they are drowning out the bugs. Most of these features should be available in the next major version of portage. But for the time being, they are just drowning out the major bugs and delaying the next version's progress. Any bugs that contain patches and any bugs for etc-update or dispatch-conf can be reopened. Sorry, I'm just not good enough with bugzilla. ;)
Reopen for duping
*** This bug has been marked as a duplicate of bug 152990 ***
