From: Daniel Goller <morfic@gentoo.org>
To: Thomas de Grenier de Latour <degrenier@easyconnect.fr>
Cc: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Re: emerge suggestions
Date: Wed, 08 Sep 2004 20:01:36 -0500 [thread overview]
Message-ID: <413FAB70.9000704@gentoo.org> (raw)
In-Reply-To: <20040909021949.37931c74@eusebe>
rather than --pretend, why not use simply 'genlop -t gcc' and see how
much time gcc TOOK to compile
s/gcc/any_package/
isn't that and the pipe with --pretend more than enough info already?
Thomas de Grenier de Latour wrote:
>On Thu, 9 Sep 2004 01:46:45 +0200
>Heiko Wundram <heikowu@ceosg.de> wrote:
>
>
>
>>I don't know when this proposal came up, I read about it on some
>>forum, some time ago.
>>
>>
>
>That's also an idea that I've seen several times (here and in
>forums). I've found this in archives:
>http://article.gmane.org/gmane.linux.gentoo.devel/10528
>There are in this thread some valid points (USE flags mainly) that
>show how difficult and time consuming this idea would be to
>actually implement.
>
>
>
--
gentoo-dev@gentoo.org mailing list
next prev parent reply other threads:[~2004-09-09 0:59 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
2004-09-09 0:19 ` Thomas de Grenier de Latour
2004-09-09 1:01 ` Daniel Goller [this message]
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=413FAB70.9000704@gentoo.org \
--to=morfic@gentoo.org \
--cc=degrenier@easyconnect.fr \
--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