From: "Marcus D. Hanwell" <linux@cryos.net>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Re: emerge suggestions
Date: Fri, 10 Sep 2004 10:29:32 +0100 [thread overview]
Message-ID: <414173FC.1060201@cryos.net> (raw)
In-Reply-To: <414085AC.50704@gentoo.org>
Danny van Dyk wrote:
> | I don't think the point was ever to be accurate, but to give a rough
> | idea. If OpenOffice.org is 1047 bash units, and bash takes 1.0 minutes
> | on your machine, then you know *about* how long OpenOffice.org will take
> | to compile. I don't think anyone is concerned with exact numbers so
> | much as ballpark figures to give them a reasonable estimate of needed
> | time.
> |
> I don't share your optimism. I already see bug reports about wrong ETAs
> ... :-/
Surely these can be dismissed as WONTFIX, and move on. There will always
be some users who expect everything to be perfect. Round up to the
nearest minute, output Estimated/Approximate/Expected emerge time: 12
minutes. This would be a great feature, and most users will not care if
it takes 15 minutes when it said 12 - it's just a lot better to have a
reasonable idea of emerge times.
If it was within 10 - 20% most of the time that is still useful to most,
and I think it will do better than that most of the time. Even if we
could make an exact estimate of emerge time issues such as other
processes using processor time etc will always throw these estimates off.
--
gentoo-dev@gentoo.org mailing list
next prev parent reply other threads:[~2004-09-10 9:29 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-08 15:40 [gentoo-dev] emerge suggestions Philippe Trottier
2004-09-08 15:47 ` [gentoo-dev] " Sebastian Bergmann
2004-09-08 16:03 ` Athul Acharya
2004-09-08 16:43 ` Chris White
2004-09-08 23:46 ` Heiko Wundram
2004-09-09 0:03 ` Ned Ludd
2004-09-09 1:01 ` Heiko Wundram
2004-09-09 13:16 ` Chris Gianelloni
2004-09-09 16:32 ` Danny van Dyk
2004-09-10 9:29 ` Marcus D. Hanwell [this message]
2004-09-09 0:19 ` Thomas de Grenier de Latour
2004-09-09 1:01 ` Daniel Goller
2004-09-08 20:10 ` Chris White
2004-09-09 5:06 ` Alin Nastac
2004-09-09 13:13 ` Chris Gianelloni
2004-09-09 2:12 ` Joseph Booker
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=414173FC.1060201@cryos.net \
--to=linux@cryos.net \
--cc=gentoo-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