emerging development-sources will only add a virtual/alsa to virtuals if the alsa use flag is set at emerge time. The virtual/alsa should always be added because development-sources is always capable of providing alsa. This becomes a problem if a user emerges development-sources and decides to add alsa support at a later stage. Emerging any package with alsa support will (attempt) to pull in alsa-driver. mm-sources implements the virtual correctly. Reproducible: Always Steps to Reproduce: 1. 2. 3.
the correct methos would be the development-sources way, as otherwise it will not pull correct dependancies when using both 2.6 and 2.4 sources. I will assign this to myself and fix later today
actuallt, simply to keep behaviour similar to that of nvidia-kernel i will make it a strict provide, and force users to manually fulfil by emerging alsa-driver if using both 2.4 and 2.6
changed
