Alan McKinnon wrote:
On Saturday 08 May 2010 18:04:42 Graham Murray wrote:
Alan McKinnon<alan.mckin...@gmail.com> writes:
xorg-drivers is just a meta package and won't remerge individual drivers
unless the version number changes. It look to me like you have an evdev
driver built against an earlier X server
Does anyone else think it would be useful for emerge to have a switch to
make it re-emerge all of the individual packages making up a
meta-package? 'emerge metapackage' does not do enough and 'emerge -e
metapackage' will rebuild too much.Either that or a utility to split a
meta-package into its constituent parts, so you could have something
like 'emerge $(qsplit xorg-drivers)'. Though in the case of xorg-drivers
the recommended 'emerge $(qlist -IC xorg-drivers/)' works just as well,
but this is just pure luck as the required packages are in a single
category which contains no other packages.
You have a snowball's chance in hell of getting that into portage.
A major concern of the devs is getting portage to rebuild *less* stuff and to
fix ebuilds yo rebuild *less* stuff and fix devs who don't grok it.
You are proposing the opposite.
I can predict the response you will get if you file a bug:
"Read the elog message"
You are right. This has been discussed a few times on -dev and
basically, it ain't going to happen. I think it is a good idea myself
since they have to be re-emerged for them to work anyway. What
difference does it make if portage does it for us or we do it manually,
after finding that command to find out which ones to rebuild.
Dale
:-) :-)