public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: byte.size226@simplelogin.com
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Migrating existing Gentoo to binpkg
Date: Tue, 19 Nov 2024 12:06:46 +0000	[thread overview]
Message-ID: <173201801028.6.1361252922715100791.499904328@simplelogin.com> (raw)
In-Reply-To: <673b0721.050a0220.36b06e.cd80@mx.google.com>

[-- Attachment #1: Type: text/plain, Size: 1559 bytes --]

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 #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 249 bytes --]

  reply	other threads:[~2024-11-19 12:07 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-11-15 12:42 [gentoo-user] Migrating existing Gentoo to binpkg byte.size226
2024-11-15 14:05 ` Jacques Montier
2024-11-15 14:15 ` Matt Jolly
2024-11-15 14:52   ` byte.size226
2024-11-15 15:41     ` Eli Schwartz
2024-11-17 14:44       ` byte.size226
2024-11-18  9:21         ` Dr Rainer Woitok
2024-11-19 12:06           ` byte.size226 [this message]
2024-11-15 15:36 ` Eli Schwartz

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=173201801028.6.1361252922715100791.499904328@simplelogin.com \
    --to=byte.size226@simplelogin.com \
    --cc=gentoo-user@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox