emerge -e is a wonderful tool, but it would be nice to eliminate some non-compilation and binary pre-compiled code from being reemerged every time emerge -e [package] is run. So I propose a new flag be added with some additional metadata in ebuilds to account for whether or not a package can be blacklisted from emerges. The reasoning for this is that it's somewhat unnecessary for one to emerge packages dealing with themes and other binary packages if they already exist in the system. For example, the following packages in theory shouldn't be reemerged (if they already are merged): gnome-icon-themes hicolor-icon-themes openoffice-bin sun-jre-bin etc... Reproducible: Always Steps to Reproduce:
Sorry. My speech was a bit ambiguous. I meant 'temporarily blacklisted from reemerging while the emerge -e operation is in effect'.
You'll have to push this to the gentoo-dev list first.
(In reply to comment #0) > The reasoning for this is that it's somewhat unnecessary for one to emerge > packages dealing with themes and other binary packages if they already exist in > the system. Many binary packages have USE flags that affect what is installed. If those flags have changed since the package was installed, what then?
yeah, just because it doesnt compile anything doesnt mean the package cant be dynamic
