From: ralfconn <mentadent47@yahoo.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] emerge - Tips and Tricks
Date: Mon, 2 Sep 2024 17:10:11 +0200 [thread overview]
Message-ID: <c697ed3f-647e-4db3-b740-b6b75777296b@yahoo.com> (raw)
In-Reply-To: <9ce08b83-1bef-400c-b79a-e6415e4d9a17@gmail.com>
Il 02/09/24 00:44, Joe ha scritto:
> Normally i run emerge -uavDU --with-bdeps=y @world when i don't want a
> reinstall of everything after a emerge --sync
>
> I run emerge -uavDN --with-bdeps=y @world when i want to reinstall or
> like the manual says if there is a use flag that has been changed by me
> or the dev.
>
My make.conf:
EMERGE_DEFAULT_OPTS="--quiet-build --keep-going --jobs 24 --load-average
24.0"
MAKEOPTS="-j24 -l24.0"
I don't know if I got the load-average and company right, anyway the
system is always responsive (Ryzen 9 with 64Gb) even when using all 24
CPU threads. The ebuilds have gotten a long way towards stability even
in ~amd64, I rarely have build problems (except when cross-compiling for
ARM, but that's a different story).
My command line is 'emerge -auDvN @world'. Let the system decide if
there are USE flag changes that require a rebuild, computers should do
the boring stuff for us 🙂
raf
prev parent reply other threads:[~2024-09-02 15:10 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-01 22:44 [gentoo-user] emerge - Tips and Tricks Joe
2024-09-01 23:56 ` Dale
2024-09-02 1:59 ` Joe
2024-09-02 5:11 ` Dale
2024-09-02 6:59 ` Wols Lists
2024-09-02 8:06 ` Michael
2024-09-02 9:17 ` [gentoo-user] " Nuno Silva
2024-09-02 3:53 ` [gentoo-user] " Matt Connell
2024-09-02 5:13 ` Dale
2024-09-02 6:55 ` Wols Lists
2024-09-02 7:19 ` Dale
2024-09-02 15:11 ` ralfconn
2024-09-03 7:49 ` Dale
2024-09-03 9:05 ` Arve Barsnes
2024-09-03 9:05 ` Arve Barsnes
2024-09-03 10:32 ` Dale
2024-09-02 15:10 ` ralfconn [this message]
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=c697ed3f-647e-4db3-b740-b6b75777296b@yahoo.com \
--to=mentadent47@yahoo.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