From: byte.size226@simplelogin.com
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Migrating existing Gentoo to binpkg
Date: Sun, 17 Nov 2024 14:44:40 +0000 [thread overview]
Message-ID: <173185468880.7.18114176355713748062.497932412@simplelogin.com> (raw)
In-Reply-To: <8e959b08-c465-435b-93d5-9dc20d1dc8cf@gentoo.org>
[-- Attachment #1: Type: text/plain, Size: 2399 bytes --]
On 15/11/2024 15:41, Eli Schwartz wrote:
> 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.
Indeed, also why shortly after my response I also added
"--usepkg-exclude 'sys-kernel/gentoo-sources virtual/*" to
EMERGE_DEFAULT_OPTS, as was recommended by one of the guides anyway :)
I did suspect packages may or may not be built from source anyway
depending on the current state of dependencies and what's available on
the upstream binhost. This is already the case for about 300 or so
packages that I have.
I was mostly interested in the binary builds due to usual suspects that
take forever to build. But also out of general curiosity, having
previously dabbled a bit into having a local binhost a few years back. I
have to admit, the flexibility is pretty sweet.
> It is only the default when using --getbinpkg, not when you are instead
> using --getbinpkgonly.
Ah! Of course, you're right. Should have calibrated my eyes better while
reading the man page.
> Your CFLAGS are irrelevant here. CFLAGS on the binhost server must be
> compatible with your local machine, or you will successfully install
> packages that then abort with SIGILL when you try to run the programs.
>
> The reverse is not true -- CFLAGS on your local machine just need to be
> compatible with, well, your local machine (where they get installed),
> not the binhost, where they don't get installed. 🙂
> ...
> Keep your existing CFLAGS that you were using before enabling the
> binhost. It's a free optimization for any packages that you ended up
> building from source anyway.
Just what I suspected 🙂
All working perfectly like a charm.
Thanks again to everyone for the responses! That, and having kept an eye
on some other discussions, the Gentoo community never seizes to
positively amaze. Unlike the respective communities of some other...
popular distros, that I shall refrain from mentioning.
Cheers,
Victor
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 249 bytes --]
next prev parent reply other threads:[~2024-11-17 14:44 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 [this message]
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=173185468880.7.18114176355713748062.497932412@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