From: Eli Schwartz <eschwartz@gentoo.org>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Migrating existing Gentoo to binpkg
Date: Fri, 15 Nov 2024 10:41:25 -0500 [thread overview]
Message-ID: <8e959b08-c465-435b-93d5-9dc20d1dc8cf@gentoo.org> (raw)
In-Reply-To: <173168238338.7.14071927941459129665.496068843@simplelogin.com>
[-- Attachment #1.1: Type: text/plain, Size: 1377 bytes --]
On 11/15/24 9:52 AM, byte.size226@simplelogin.com wrote:
> Thank you, both!
>
>
> On 15/11/2024 14:05, Jacques Montier wrote:
>> What if you try this :
>> emerge -auvDN --getbinpkgonly --with-bdeps=y --binpkg-respect-use=y --
>> keep-going world
>
> This does indeed suggest to replace existing builds with the upstream
> binary ones. I traced this to --getbinpkgonly which seems to force the
> use of the binary packages over source builds where possible.
>
> There are, however, minor differences between this and my earlier
> example with --rebuilt-binaries. Using "--getbinpkgonly" suggests a few
> downgrades, including to sys-kernel/gentoo-sources.
gentoo-sources is not part of the guaranteed package set for the
binhost. Any package *may* end up built on the binhost, either as a
dependency for another package that stops being a dependency because the
other package has changed, or due to the fact that we run a few
different build configurations, including choosing a couple packages by
lottery each day. Those may be available only for an older version in
the ::gentoo tree if they don't get lucky a second time.
> "--binpkg-respect-use=y" makes no difference as emerge(1) suggests this
> is the default.
It is only the default when using --getbinpkg, not when you are instead
using --getbinpkgonly.
--
Eli Schwartz
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 236 bytes --]
next prev parent reply other threads:[~2024-11-15 15:41 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 [this message]
2024-11-17 14:44 ` byte.size226
2024-11-18 9:21 ` Dr Rainer Woitok
2024-11-19 12:06 ` byte.size226
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=8e959b08-c465-435b-93d5-9dc20d1dc8cf@gentoo.org \
--to=eschwartz@gentoo.org \
--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