usecase: disabling FEATURE "buildpkg" for all live-builds /etc/portage/env/nobuildpkg: FEATURES="-buildpkg" /etc/portage/package.env: =*/*-9999 nobuildpkg atm "=*/*-9999" is an invalid atom This would also enable one to simply unlock all live-builds via package.accept_keywords. I can think of a few more usecases... Reproducible: Always
Usecase: using experimental branch perl on stable branch *perl*/* ~amd64 *perl*/* is an invalid atom Reproducable: Always
(In reply to comment #0) > usecase: disabling FEATURE "buildpkg" for all live-builds > > /etc/portage/env/nobuildpkg: FEATURES="-buildpkg" > /etc/portage/package.env: =*/*-9999 nobuildpkg > > atm "=*/*-9999" is an invalid atom > > This would also enable one to simply unlock all live-builds via > package.accept_keywords. I can think of a few more usecases... Yes, maybe be something like glep 54 would be nicer, but being able to match *9999* would be good enough. (In reply to comment #1) > *perl*/* is an invalid atom Really? I've tested *perl*/* in package.accept_keywords and it works for me.
This is fixed in git: http://git.overlays.gentoo.org/gitweb/?p=proj/portage.git;a=commit;h=3e84557b91b43ea6924bbab8a3d477509513cac8 Use =*/*-*9999* to mask *9999* packages. It only works with *digits* patterns.
This is fixed in 2.1.11.9 and 2.2.0_alpha120.
(In reply to comment #2) > Really? I've tested *perl*/* in package.accept_keywords and it works for me. OK. I was on Portage 2.11.8. thanks for the fix.
