From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gentoo-dev-return-5001-arch-gentoo-dev=gentoo.org@gentoo.org>
Received: (qmail 31034 invoked by uid 1002); 25 Jul 2003 18:34:08 -0000
Mailing-List: contact gentoo-dev-help@gentoo.org; run by ezmlm
Precedence: bulk
List-Post: <mailto:gentoo-dev@gentoo.org>
List-Help: <mailto:gentoo-dev-help@gentoo.org>
List-Unsubscribe: <mailto:gentoo-dev-unsubscribe@gentoo.org>
List-Subscribe: <mailto:gentoo-dev-subscribe@gentoo.org>
List-Id: Gentoo Linux mail <gentoo-dev.gentoo.org>
X-BeenThere: gentoo-dev@gentoo.org
Received: (qmail 28407 invoked from network); 25 Jul 2003 18:34:07 -0000
From:	Svyatogor <svyatogor@gentoo.org>
To:	gentoo-dev@gentoo.org
In-Reply-To: <200307251956.27193.ripat@xs4all.nl>
References: <200307251956.27193.ripat@xs4all.nl>
Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="=-uCTl1jUp26VN60K1xZlq"
Message-Id: <1059160421.2178.5.camel@sergey.swdevelopers.net>
Mime-Version: 1.0
X-Mailer: Ximian Evolution 1.4.3 
Date:	25 Jul 2003 22:13:42 +0300
Subject: Re: [gentoo-dev] compile time statistics
X-Archives-Salt: 23b7ab61-5238-43c3-8f99-e1cb87df7b74
X-Archives-Hash: cabc63cbde9e6e58643f085e8a5cc5c5

--=-uCTl1jUp26VN60K1xZlq
Content-Type: text/plain; charset=KOI8-R
Content-Transfer-Encoding: quoted-printable

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?

=F7 ?? 25.07.2003, =D7 20:56, Rutger Lubbers =D0=C9=DB=C5=D4:
> People,
>=20
> This mail is about a question. The question is "how long does package x.y=
.z=20
> take to compile on my machine?" Now my idea is, we have the emerge.log fi=
le=20
> and can obtain some data from it, so we might "predict" that compile time=
 for=20
> that user.
>=20
> To get a fairly good prediction I need data. To get data I perhaps need a=
=20
> prediction. Which needs data. So at the moment I don't know what to do.=20
>=20
> One part I have finished right now, I can get the compile times from the=20
> emerge.log and submit it to a central database (see http://ripat.xs4all.n=
l).
> Some "basic" querying I can do too.
>=20
> My questions to you is:
> - would this be a nice feature to have?
> - would you be willing to provide me with compile time statistics?
> - do you have any hints / ideas what I can do to get this from a no datal=
ess=20
> project to a data having project?
>=20
> Thanks,
>=20
>=20
> Rutger Lubbers
>=20
>=20
> --
> gentoo-dev@gentoo.org mailing list
--=20
Let the Force be with us!
Sergey Kuleshov <svyatogor@gentoo.org>
Pulic Key: http://dev.gentoo.org/~sergey/gentoo-gpg

--=-uCTl1jUp26VN60K1xZlq
Content-Type: application/pgp-signature; name=signature.asc
Content-Description: =?koi8-r?Q?=FC=D4=C1?= =?koi8-r?Q?_=DE=C1=D3=D4=D8?=
	=?koi8-r?Q?_=D3=CF=CF=C2=DD=C5=CE=C9=D1?=
	=?koi8-r?Q?_=D0=CF=C4=D0=C9=D3=C1=CE=C1?=
	=?koi8-r?Q?_=C3=C9=C6=D2=CF=D7=CF=CA?=
	=?koi8-r?Q?_=D0=CF=C4=D0=C9=D3=D8=C0?=

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.2 (GNU/Linux)

iD8DBQA/IYFlbYNN+aDJgscRAmZLAKCzkocIAnjdE6wVcUK2Wea262UJZQCgpRwR
GHeBZhrDrYNH3XBn+CN+8+g=
=RGXg
-----END PGP SIGNATURE-----

--=-uCTl1jUp26VN60K1xZlq--