public inbox for gentoo-portage-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Dan Armak <danarmak@gentoo.org>
To: gentoo-portage-dev@lists.gentoo.org
Subject: Re: [gentoo-portage-dev] emerge progress meter
Date: Sat, 21 Feb 2004 12:44:04 +0200	[thread overview]
Message-ID: <200402211244.23109.danarmak@gentoo.org> (raw)
In-Reply-To: <4036F344.3050501@skylineaero.com>

[-- Attachment #1: Type: text/plain, Size: 1262 bytes --]

On Saturday 21 February 2004 07:57, Andrew Gaffney wrote:
> I know there has been talk in the past about having a feature in portage
> that will just display a progress meter during compilation of a package,
> instead of the 'make' output. One idea was to walk the source tree and
> process the Makefile's to determine how many 'make' operation would need to
> be done and using that to determine compilation progress. Has anyone got
> any working code? If not, I'm starting on a proof-of-concept wrapper script
> in Perl just to see how it can be done.

I know working code exists, because I tried it out a few months ago. The only 
reference I could find now (not sure if it's the same one I used before, or 
if this one even works) is 
http://lists.linux.it/pipermail/bglug/2003-December/004774.html - look at the 
quoted part in English. I can't find the orig message quoted here, but 
haven't tried very hard. Perhaps inside the sources linked from there 
(http://www.ces.clemson.edu/~eduffy/emerge-progress.tar) there's more info.

HTH,

-- 
Dan Armak
Gentoo Linux developer (KDE)
Matan, Israel
Public GPG key: http://dev.gentoo.org/~danarmak/danarmak-gpg-public.key
Fingerprint: DD70 DBF9 E3D4 6CB9 2FDD  0069 508D 9143 8D5F 8951

[-- Attachment #2: signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

      reply	other threads:[~2004-02-21 10:44 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-02-21  5:57 [gentoo-portage-dev] emerge progress meter Andrew Gaffney
2004-02-21 10:44 ` Dan Armak [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=200402211244.23109.danarmak@gentoo.org \
    --to=danarmak@gentoo.org \
    --cc=gentoo-portage-dev@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