| 1 |
Am 24.03.2013 18:14, schrieb Jarry: |
| 2 |
> On 24-Mar-13 17:46, Neil Bothwick wrote: |
| 3 |
>> On Sun, 24 Mar 2013 17:26:03 +0100, Jarry wrote: |
| 4 |
>> |
| 5 |
>>> [ebuild N ] sys-kernel/gentoo-sources-3.7.10:3.7.10 USE="-build |
| 6 |
>>> -deblob -symlink" 68,335 kB |
| 7 |
>>> [ebuild N ] virtual/linux-sources-0 0 kB |
| 8 |
>>> [ebuild R ] sys-apps/kmod-12-r1 USE="tools zlib -debug -doc -lzma |
| 9 |
>>> -static-libs" KERNEL="(linux%*)" 0 kB |
| 10 |
>> |
| 11 |
>>> Why in the heavens name should be gentoo-sources pulled in as |
| 12 |
>>> dependency of whatever? |
| 13 |
>> |
| 14 |
>> As a dependency of virtual-sources, which is probably pulled in by kmod. |
| 15 |
>> Adding --tree would have told you for sure. |
| 16 |
>> |
| 17 |
>> You may get away with adding gentoo-sources to package.provided. |
| 18 |
> |
| 19 |
> Thanks, this works (never heard of this file before). But there |
| 20 |
> is one small problem: no wildcards are allowed, so whenever new |
| 21 |
> sorces come I'll have to edit package.provided again, and again |
| 22 |
|
| 23 |
No, that's not true. Here's the quote from the man page: |
| 24 |
|
| 25 |
Portage will not attempt to update a package that is listed here |
| 26 |
unless another package explicitly requires a version that is newer than |
| 27 |
what has been listed. Dependencies that are satisfied by |
| 28 |
package.provided entries may cause installed packages satisfying |
| 29 |
equivalent dependencies to be removed by emerge(1) --depclean actions |
| 30 |
(see the ACTIONS section of the emerge(1) man page for more information). |
Archives