From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 16546 invoked by uid 1002); 19 Sep 2003 15:11:34 -0000 Mailing-List: contact gentoo-dev-help@gentoo.org; run by ezmlm Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-dev@gentoo.org Received: (qmail 20386 invoked from network); 19 Sep 2003 15:11:33 -0000 From: Paul de Vrieze To: gentoo-dev@gentoo.org Date: Fri, 19 Sep 2003 17:11:18 +0200 User-Agent: KMail/1.5.2 References: <1492EAE0-E109-11D7-8740-000A95750E24@xs4all.nl> In-Reply-To: <1492EAE0-E109-11D7-8740-000A95750E24@xs4all.nl> MIME-Version: 1.0 Content-Type: multipart/signed; protocol="application/pgp-signature"; micalg=pgp-sha1; boundary="Boundary-02=_fyxa/Vj2UQNJl1w"; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <200309191711.27043.pauldv@gentoo.org> X-Spam-Status: No, hits=-9.4 required=5.0 tests=BAYES_01,EMAIL_ATTRIBUTION,IN_REP_TO,PGP_SIGNATURE_2, QUOTED_EMAIL_TEXT,REFERENCES,REPLY_WITH_QUOTES, USER_AGENT_KMAIL autolearn=ham version=2.55-uvt4 X-Spam-Checker-Version: SpamAssassin 2.55-uvt4 (1.174.2.19-2003-05-19-exp) X-Virus-Scanned: by AMaViS-ng (Milter interface) Subject: Re: [gentoo-dev] Some suggestions X-Archives-Salt: f5297807-024c-495b-a76c-84b479bb5871 X-Archives-Hash: 754ed90027c08df9267f32a0db6d1fae --Boundary-02=_fyxa/Vj2UQNJl1w Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Content-Description: signed data Content-Disposition: inline On Sunday 07 September 2003 09:58, Rutger Lubbers wrote: > > On Sat, 6 Sep 2003 21:50:42 +0200 > > > > Marius Mauch wrote: > >> A accurate progress bar is nearly impossible as compile times differ > >> from package to package > > > > Maybe maintainers could fill in the ebuilds a kind of approximative > > compile time from their experience, which would be relative to a > > well know reference time (a kernel compilation with default options, or > > something like this). It doesn't need to be very accurate. > > One could easily obtain those compile times from the emerge log file. > See http://ripat.xs4all.nl/gentoo/stats/ (parse_log.py) for an > implementation. > Perhaps this can be made part of the gentoo-stats package. > > Rutger I believe the only viable way to get reasonable estimates is to count the=20 amount of gcc/g++/whatever compiler invocations from the make log for most= =20 options, and use those. That will only give an intra-package idea though. T= he=20 difference in compilation length for files can differ a lot between differe= nt=20 packages, esp. the difference between gcc and g++ can be big if lots of=20 headers get pulled in. Paul =2D-=20 Paul de Vrieze Gentoo Developer Mail: pauldv@gentoo.org Homepage: http://www.devrieze.net --Boundary-02=_fyxa/Vj2UQNJl1w Content-Type: application/pgp-signature Content-Description: signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.2 (GNU/Linux) iD8DBQA/axyfbKx5DBjWFdsRAvHbAKDP3P0b7oItp2eRZtXueXM0srJDYQCfcAsT yeZxRP6Alme9kNkuNLKWEgM= =WE/y -----END PGP SIGNATURE----- --Boundary-02=_fyxa/Vj2UQNJl1w--