| 1 |
Hello all, |
| 2 |
|
| 3 |
There is a discepancy in the way that mm-sources and development-sources |
| 4 |
handles virtual/alsa. Have a look: |
| 5 |
|
| 6 |
bash-2.05b$ grep alsa /usr/portage/sys-kernel/development-sources/ |
| 7 |
development-sources-2.6.0_beta5-r11.ebuild |
| 8 |
IUSE="alsa" |
| 9 |
[ -n "$(use alsa)" ] && PROVIDE="${PROVIDE} virtual/alsa" |
| 10 |
|
| 11 |
bash-2.05b$ grep alsa /usr/portage/sys-kernel/mm-sources/ |
| 12 |
mm-sources-2.6.0_beta5-r4.ebuild |
| 13 |
virtual/alsa" |
| 14 |
|
| 15 |
In other words, development-sources will provide virtual/alsa only if the use |
| 16 |
flag is set when it is emerged. mm-sources, however, will provide virtual/ |
| 17 |
alsa regardless. Which is the correct behaviour? |
| 18 |
|
| 19 |
Personally, I think mm-sources is the better option. The reason being if a |
| 20 |
user decides to use alsa after emerging development-sources by adding alsa to |
| 21 |
the use flags, portage will see no virtual/alsa and try and pull in |
| 22 |
alsa-driver. |
| 23 |
|
| 24 |
Any opinions before I post a bug? |
| 25 |
|
| 26 |
Regards, |
| 27 |
Jason |
| 28 |
|
| 29 |
-- |
| 30 |
gentoo-dev@g.o mailing list |
Archives