From: Alan McKinnon <alan.mckinnon@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Controlling emerges
Date: Mon, 18 Sep 2023 15:48:46 +0200 [thread overview]
Message-ID: <CAEdtorZ=wZ-zQ4AJ_swztJ4gsgFjGMekcjXgYgGANJjn1Q1+kA@mail.gmail.com> (raw)
In-Reply-To: <8292274.T7Z3S40VBb@wstn>
[-- Attachment #1: Type: text/plain, Size: 646 bytes --]
On Mon, Sep 18, 2023 at 3:44 PM Peter Humphrey <peter@prh.myzen.co.uk>
wrote:
>
>
> It may be less complex than you think, Jack. I envisage a package being
> marked
> as solitary, and when portage reaches that package, it waits until all
> current
> jobs have finished, then it starts the solitary package with the
> environment
> specified for it, and it doesn't start the next one until that one has
> finished.
> The dependency calculation shouldn't need to be changed.
>
> It seems simple the way I see it.
>
How does that improve emerge performance overall?
--
Alan McKinnon
alan dot mckinnon at gmail dot com
[-- Attachment #2: Type: text/html, Size: 1112 bytes --]
next prev parent reply other threads:[~2023-09-18 13:49 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-18 12:00 [gentoo-user] Controlling emerges Peter Humphrey
2023-09-18 12:59 ` Jack
2023-09-18 13:44 ` Peter Humphrey
2023-09-18 13:48 ` Alan McKinnon [this message]
2023-09-18 16:03 ` Peter Humphrey
2023-09-18 16:13 ` Alan McKinnon
2023-09-18 17:54 ` Laurence Perkins
2023-09-18 22:44 ` William Kenworthy
2023-09-19 9:09 ` Peter Humphrey
2023-09-19 9:14 ` William Kenworthy
2023-09-19 9:37 ` Andreas Fink
2023-09-19 9:48 ` Peter Humphrey
2023-09-19 10:06 ` Rich Freeman
2023-09-19 10:13 ` William KENWORTHY
2023-09-18 17:59 ` Michael
2023-09-18 18:10 ` John Blinka
2023-09-18 18:18 ` Dale
2023-09-18 18:49 ` Rich Freeman
2023-09-19 12:28 ` Peter Humphrey
2023-09-20 22:06 ` Wol
2023-09-21 19:26 ` Laurence Perkins
2023-09-21 20:30 ` Tsukasa Mcp_Reznor
2023-09-22 1:13 ` Dale
2023-09-22 7:13 ` Michael
2023-09-22 10:07 ` Rich Freeman
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='CAEdtorZ=wZ-zQ4AJ_swztJ4gsgFjGMekcjXgYgGANJjn1Q1+kA@mail.gmail.com' \
--to=alan.mckinnon@gmail.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