| 1 |
Georgi Georgiev wrote: |
| 2 |
> maillog: 19/06/2006-11:13:33(+0000): Alec Warner types |
| 3 |
> |
| 4 |
>>Portage currently exports $KV as the current kernel version. We detect |
| 5 |
>>this by attempting to mess around with the things in /usr/src/linux |
| 6 |
>>(.config, make files, etc...) |
| 7 |
>> |
| 8 |
>>This is duplicating the superb efforts of the kernel team and of |
| 9 |
>>linux-info eclass. As such I would like to deprecate $KV in favor of |
| 10 |
>>using linux-info eclass. I don't see the need for portage to export $KV |
| 11 |
>>into the environment for all packages. |
| 12 |
>> |
| 13 |
>>There are a few packages left that use this. There will be a tracker |
| 14 |
>>bug shortly. Mostly this mail is just a heads up ;) |
| 15 |
> |
| 16 |
> |
| 17 |
> But any kind of checks against something in $KERNEL_DIR are just wrong, |
| 18 |
> wrong, wrong. The only exception being when the ebuild is building |
| 19 |
> something *against* those sources (kernel modules, and that's it). |
| 20 |
> |
| 21 |
> It's annoying to have virtual/linux-sources pulled as a dep of gnupg, |
| 22 |
> iptables or any other package that can do fine without them. |
| 23 |
> |
| 24 |
In many cases those packages are looking for a specific kernel feature |
| 25 |
to make sure support is enabled for it. |
| 26 |
|
| 27 |
You could argue that in the case where you aren't compiling against the |
| 28 |
kernel that support being enabled isn't critical, but that is a |
| 29 |
discussion you need to have with the package maintainers. |
| 30 |
-- |
| 31 |
gentoo-dev@g.o mailing list |
Archives