It's a features request (didn't find way to do that in doc/forum so might not exist) Here are the features i request for emerge: - Emerge should not only tell us an ebuild is mask but also gives us reason why it is mask: ie (not a real one) : vlc-0.6.2.ebuild mask because of : GLSA-X-X-X or vlc-0.6.2 mask because of : http streaming broken... See why the info is important: if i use vlc but NEVER use it to do HTTP streaming then i could safely use it and discard the fact this ebuild is mask... (it could be easy done by adding a comment in package.mask that will be display by emerge when using --verbose) - If i understand using ACCEPT_KEYWORDS="~x86" will bypass mask limitation for my arch and so try to install files But i don't like that: it will try install files that are really too much dangerous for me (common user), for exemple i don't want have the latest version of something if it's still an alpha or beta version :( Some ebuilds are mask because they don't work on some arch and so everyone without the broken arch don't get them... So i want emerge to build a new token something like "~x86-stable"... So i could use these ebuilds that are mask for no reason for my platform! It's not clear maybe, so take that example: vlc.0.7.2 is mask for me, but if i do ACCEPT_KEYWORDS="~x86" it compile fine and works fine ! vlc 0.7.2 has been release since 21 may 2004 and it still mask in portage :( So i suggest these new tokens so ppl could get vlc-0.7.2 without to wait months! Another exemple is net-p2p/mldonkey ebuilds: Emerge wants only me to grab the 2.5.16-r8 ebuild while the mldonkey website state the latest STABLE release is 2.5.22 ! so i want emerge to have ebuilds set as is mldonkey-2.5.16-rx x86 mldonkey-2.5.22 ~x86-stable (state stable by the program maker, if it don't work, mask it to remove it from ~x86-stable list) mldonkey-2.5.28 ~x86 I don't want enable "~x86" in make.conf because many ebuilds are broken or use unstable release of programs, but it's not cool to wait months for getting a "stable" (as videolan says) version ! Another example: i'm using a geforce 6800 and i can only make it work with the nvidia 1.0.6111 but emerge keep remove them to install the 1.0.5336-r4 :( The 1.0.6111 are mask by the ~x86 flag but they work for me ! But if i use the ~x86 flag in make.conf i will grab programs i don't want example: [ebuild U ] app-editors/quanta-3.3_pre20040506 [3.2.3] the 3.3_pre20040506 of quanta is really something i don't want install ! Quanta is my editor and i want it as stable as possible (don't want it to play with my text) and it's clear a prexxx version isn't something we could called STABLE! I hope it's clear now :/ x86 - ebuild of known stable version ~x86-stable - ebuild of version "state" stable (trust program maker at first) ~x86 - ebuild of work-in-progress, beta... version package.mask - mask ebuild that really have a flaw (could be x86, ~x86-stable or ~x86 ebuilds) Reproducible: Always Steps to Reproduce: 1. 2. 3. Actual Results: really unsure you will understand Expected Results: Ppl understand my point of view :D
why not use /etc/portage/package.keywords?
Because if i put vlc in package.keywords i will grab the "vlc-0.7.2prexxx" and i don't want have that !!! Reread examples ! But if i use the ~x86 flag in make.conf i will grab programs i don't want example: [ebuild U ] app-editors/quanta-3.3_pre20040506 [3.2.3] So if i put quanta in package.keywords i will grab the stupid quanta-3.3_pre20040506 and i don't want it ! Want another example, seems you need more... I do want grub new version but not versions like this ! [ebuild U ] sys-boot/grub-0.95.20040823 [0.94-r1] Or could i put a specific version in package.keywords ? Anyway this method isn't fast (need to add every program version i wish by hands)
