Currently, linux-mod.eclass has the following: DEPEND="virtual/linux-sources sys-apps/sed virtual/modutils pcmcia? ( sys-apps/pcmcia-cs )" In my opinion, this means that it should also contain the line IUSE="pcmcia". I had a hell of a time figuring out why some packages wanted to install pcmcia-cs (which was only giving me errors anyway).
Agreed. Good spot. Is now comitted into the tree.
The current solution makes _all_ linux-mod derived ebuilds have USE="pcmcia" even though the ebuild doesn't have anything to use the pcmcia flag for. I think the correct solution would be to enforce ebuilds, that use the pcmcia USE flag to have IUSE="pcmcia".
hmm, apparently so :) After looking at the list there is only: hostap-driver linux-wlan-ng orinoco which inherits pcmcia (originally). brix, since this is your area can I leave you with these?
I've ensured that all of the above mentioned ebuilds include IUSE=pcmcia - and I've removed the IUSE=pcmcia from linux-mod.eclass (again). Closing as FIXED.
Hm, so if I install for example media-tv/rivatv, or any of the other 78 packages that inherit linux-mod, I'll have no way of figuring out why sys-apps/pcmcia is being pulled as a dependency? Re: Comment #2 > The current solution makes _all_ linux-mod derived ebuilds have > USE="pcmcia" even though the ebuild doesn't have anything to use the > pcmcia flag for. That's not true. It has *everything* to do with the ebuild using the pcmcia flag to pull a dependency.
Can you please also remove that line then? DEPEND="pcmcia? ( sys-apps/pcmcia-cs )" All pkges that need it should depend on pcmcia-cs anyway .. Another thing is: SHould we even depend on sys-app/pcmcia-cs now, that pcmciautils can replace it? Maybe create a virutal?
A virtual will be created once pcmciautils enters the tree.
