From: Eli Schwartz <eschwartz@gentoo.org>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Prebuilt packages
Date: Tue, 11 Feb 2025 11:02:04 -0500 [thread overview]
Message-ID: <d1c2d86f-c3df-42ab-be83-bcd237cf2780@gentoo.org> (raw)
In-Reply-To: <4631075.LvFx2qVVIh@cube>
[-- Attachment #1.1: Type: text/plain, Size: 2351 bytes --]
On 2/11/25 10:22 AM, Peter Humphrey wrote:
> Greetings,
>
> I was delighted to see Gentoo's venture into prebuilt packages, having two
> small machines here. However, experience has rubbed some of the shine off.
>
> Any time I update the system, if there's no package with the right USE flags,
> or even no package at all, I've built from source in the traditional way.
> Later, on running 'eclean-pkg --deep --package-names', I get a load of
> invalid-package warnings. I just assumed that was harmless.
>
> More serious, I'm sure, is the mess I'm getting into with 'emerge -k' and/or
> 'emerge -K'. It became so bad that I tried reinstalling from scratch today. I
> couldn't make it work at all - at one stage I was told to emerge @preserved-
> rebuild, whereupon it insisted on installing the nouveau drivers.
> Preposterous.
>
> Can portage not operate a mixed prebuilt and home-grown system?
I don't understand what you're trying to say at all.
emerge --getbinpkg is *already* a mixed prebuilt and home-grown system.
And emerge --getbinpkgonly is a modification to getbinpkg that says you
don't want a mixed system, you want exclusively prebuilt. Using the
*only variant is a personal choice you aren't obligated to make.
You haven't actually provided details about why you think there's a
problem though. You have said:
- if there are no packages available for your configuration, you have
"built from source in the traditional way", which emerge already does
*automatically* unless you explicitly tell it not to. Should I be
concluding from here that you first tried the *only variant, then when
that failed you disabled fetching binary packages altogether in a fit
of frustration?
- you installed Gentoo from scratch because "it" became so bad. What is
"it"? I am finding it hard to imagine a situation where there could be
an "it", let alone deduce the details of what "it" constitutes.
- who told you to emerge @preserved-rebuild, what was it in relation to,
what was the dependency graph that claimed it was installing nouveau?
- "I get a load of invalid-package warnings. I just assumed that was
harmless". Failure to delete a useless unneeded file is most likely
harmless, yes. More details would require you saying more here.
--
Eli Schwartz
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 236 bytes --]
next prev parent reply other threads:[~2025-02-11 16:03 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-11 15:22 [gentoo-user] Prebuilt packages Peter Humphrey
2025-02-11 16:02 ` Eli Schwartz [this message]
2025-02-11 17:06 ` Peter Humphrey
2025-02-11 17:26 ` Eli Schwartz
2025-02-12 0:37 ` Peter Humphrey
2025-02-12 1:35 ` Eli Schwartz
2025-02-11 23:04 ` Mickaël Bucas
2025-02-11 23:31 ` Mickaël Bucas
2025-02-12 1:25 ` Eli Schwartz
2025-02-12 12:07 ` Peter Humphrey
2025-02-12 18:25 ` Jay Faulkner
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=d1c2d86f-c3df-42ab-be83-bcd237cf2780@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