public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Peter Humphrey <peter@prh.myzen.co.uk>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Portage improved
Date: Tue, 05 Nov 2024 06:58:37 +0000	[thread overview]
Message-ID: <2770570.mvXUDI8C0e@cube> (raw)
In-Reply-To: <4967547.31r3eYUQgx@cube>

On Thursday 31 October 2024 11:56:41 GMT Peter Humphrey wrote:
> On Friday 11 October 2024 11:49:18 GMT I wrote:
> > On Saturday 14 September 2024 13:05:26 BST Peter Humphrey wrote:
> > > Just one little fly in the ointment: the status string became too long
> > > to
> > > show properly. Perhaps shorter phrases could be used, or numbers limited
> > > to two digits, or the 80-character line limit exceeded while running in
> > > an
> > > x-term.
> > 
> > And indeed the line limit has been relaxed: it uses the full 90 characters
> > of my Konsoles.
> 
> More to do yet though. The merge-wait idea works well with humongous
> packages like nodejs and the web engines, but it's too cautious with
> ordinary ones. I've been building (too many) new systems over the last
> fortnight, and when there are, say, a hundred packages to compile, the load
> steadies out at about 4, with several more in merge-wait. This is with i24
> l30 in make.conf.

There's also a logic problem. When a package enters the Installing phase, it's 
shown instead as Merge Wait, or it's added to that queue.

-- 
Regards,
Peter.





  parent reply	other threads:[~2024-11-05  6:58 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-09-14 12:05 [gentoo-user] Portage improved Peter Humphrey
2024-10-11 10:49 ` Peter Humphrey
2024-10-31 11:56   ` Peter Humphrey
2024-11-03 12:56     ` Wols Lists
2024-11-03 23:18       ` Peter Humphrey
2024-11-03 23:23         ` Peter Humphrey
2024-11-05  6:58     ` Peter Humphrey [this message]
2024-11-08 14:36       ` Peter Humphrey

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=2770570.mvXUDI8C0e@cube \
    --to=peter@prh.myzen.co.uk \
    --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