On 18/11/2024 09:21, Dr Rainer Woitok wrote:
                                            I also added
"--usepkg-exclude 'sys-kernel/gentoo-sources virtual/*" to
EMERGE_DEFAULT_OPTS, as was recommended by one of the guides anyway :)

Hm, I can't see any logic in Gentoo developers wasting electrons and key
strokes to provide at least  one "sys-kernel/gentoo-sources"  and a ple-
thora of  "virtual/*" packages  on the binhost  and then advising to ex-
clude them from being used.  Which guide recommended that?


The in-depth "Binary package guide" [1], section 3.7 "Additional client settings".

I guess I misspoke by referring to it as "recommendation" but the example given, which excludes "sys-kernel/gentoo-sources", can be seen as de facto recommendation as it is quite sound.

It makes sense as the "sys-kernel/gentoo-sources" package does not have a "binary" package in the sense of a running kernel, which is provided by "sys-kernel/gentoo-kerne
l-bin".

Emerging gentoo-source simply shows it as an "[ebuild]" which is what I would expect for a package that is supposed to only contain source code. Meanwhile, gentoo-kernel-bin is correctly being pulled from the binhost as "[binary]".

As for "virtual/", well they don't really contain anything so there's no binary to provide. I'm not sure if there's anything "[binary]" on the binhost for them as I would struggle to see what that would be other than a label for a given... version/revision?

Regards,
Victor

[1] https://wiki.gentoo.org/wiki/Binary_package_guide

Attachment: signature.asc
Description: OpenPGP digital signature

Reply via email to