public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Rutger Lubbers <ripat@xs4all.nl>
To: gentoo-dev@gentoo.org
Subject: Re: [gentoo-dev] compile time statistics
Date: Fri, 25 Jul 2003 20:46:16 +0200	[thread overview]
Message-ID: <200307252046.16452.ripat@xs4all.nl> (raw)
In-Reply-To: <1059160421.2178.5.camel@sergey.swdevelopers.net>

I believe that that is possible... That's why I started this.
Only getting data into the ebuilds... thats something else... 
I could obtain data for a package class (net-www) or a package 
(net-www/mozilla) or for a version (net-www/mozilla-0.0.1-alpha). 
Now to port that data back.... thats difficult... perhaps emerge sync should 
get the data for your cpu type and we should modify emerge so that it takes 
advantage of that info.....

> I was actually thinking of making this proposal :)
> Just a small comment. In LFS you can find estimate compile time in SBU
> (Standart Bash Units - time required to compile bash). It would be nice
> if we could include this kind of information into ebuild. Any ideas on
> whether that would be possible to do?


--
gentoo-dev@gentoo.org mailing list


  reply	other threads:[~2003-07-25 18:45 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-07-25 17:56 [gentoo-dev] compile time statistics Rutger Lubbers
2003-07-25 18:49 ` Chris Gianelloni
2003-07-25 19:13 ` Svyatogor
2003-07-25 18:46   ` Rutger Lubbers [this message]
2003-07-25 18:51   ` Werner Van Belle
2003-07-26  9:56     ` Håvard Wall
2003-07-26 10:05       ` Stuart Herbert
2003-07-26 10:11         ` Håvard Wall
2003-07-26 13:34         ` Rutger Lubbers
2003-07-26 13:50       ` Chris Gianelloni
2003-08-05 16:03         ` Stewart Honsberger
2003-07-25 18:54   ` Chris Gianelloni
2003-07-26 10:35 ` Håvard Wall
2003-07-26  8:47   ` FRLinux
2003-07-26 14:50     ` Rutger Lubbers
2003-07-26 15:13       ` Lisa Marie Seelye
2003-07-26 15:21       ` Tal Peer
2003-07-26 15:30         ` Rutger Lubbers

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=200307252046.16452.ripat@xs4all.nl \
    --to=ripat@xs4all.nl \
    --cc=gentoo-dev@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