| 1 |
On 09/28/03 Jason Stubbs wrote: |
| 2 |
|
| 3 |
> Hello all, |
| 4 |
> |
| 5 |
> There is a discepancy in the way that mm-sources and |
| 6 |
> development-sources handles virtual/alsa. Have a look: |
| 7 |
> |
| 8 |
> bash-2.05b$ grep alsa /usr/portage/sys-kernel/development-sources/ |
| 9 |
> development-sources-2.6.0_beta5-r11.ebuild |
| 10 |
> IUSE="alsa" |
| 11 |
> [ -n "$(use alsa)" ] && PROVIDE="${PROVIDE} virtual/alsa" |
| 12 |
> |
| 13 |
> bash-2.05b$ grep alsa /usr/portage/sys-kernel/mm-sources/ |
| 14 |
> mm-sources-2.6.0_beta5-r4.ebuild |
| 15 |
> virtual/alsa" |
| 16 |
> |
| 17 |
> In other words, development-sources will provide virtual/alsa only if |
| 18 |
> the use flag is set when it is emerged. mm-sources, however, will |
| 19 |
> provide virtual/ alsa regardless. Which is the correct behaviour? |
| 20 |
> |
| 21 |
> Personally, I think mm-sources is the better option. The reason being |
| 22 |
> if a user decides to use alsa after emerging development-sources by |
| 23 |
> adding alsa to the use flags, portage will see no virtual/alsa and try |
| 24 |
> and pull in alsa-driver. |
| 25 |
> |
| 26 |
> Any opinions before I post a bug? |
| 27 |
|
| 28 |
PROVIDE should not be conditional and it doesn't even make sense in this |
| 29 |
case as the kernel has alsa modules independent of the alsa USE flag. So |
| 30 |
file a bug for development sources. |
| 31 |
|
| 32 |
Marius |
| 33 |
|
| 34 |
-- |
| 35 |
Public Key at http://www.genone.de/info/gpg-key.pub |
| 36 |
|
| 37 |
In the beginning, there was nothing. And God said, 'Let there be |
| 38 |
Light.' And there was still nothing, but you could see a bit better. |
Archives