1 |
-----BEGIN PGP SIGNED MESSAGE----- |
2 |
Hash: SHA1 |
3 |
|
4 |
Hmmm, |
5 |
|
6 |
Altough it's a nice proposal that would be really usefull, I still think there |
7 |
are some serious problems involved. Compilation time is non lineair. |
8 |
Depending on how much cache, how much memory, how fast your hard-disk is, |
9 |
what your bus-speed is and above all, what the user is doing at the same time |
10 |
while upgrading his machine will seriously impact compilation time. All of |
11 |
these factors are very difficult to take into account. |
12 |
|
13 |
With kind regards, |
14 |
|
15 |
Werner,- |
16 |
|
17 |
On Friday 25 July 2003 21:13, Svyatogor wrote: |
18 |
> I was actually thinking of making this proposal :) |
19 |
> Just a small comment. In LFS you can find estimate compile time in SBU |
20 |
> (Standart Bash Units - time required to compile bash). It would be nice |
21 |
> if we could include this kind of information into ebuild. Any ideas on |
22 |
> whether that would be possible to do? |
23 |
> |
24 |
> ÷ ?? 25.07.2003, × 20:56, Rutger Lubbers ÐÉÛÅÔ: |
25 |
> > People, |
26 |
> > |
27 |
> > This mail is about a question. The question is "how long does package |
28 |
> > x.y.z take to compile on my machine?" Now my idea is, we have the |
29 |
> > emerge.log file and can obtain some data from it, so we might "predict" |
30 |
> > that compile time for that user. |
31 |
> > |
32 |
> > To get a fairly good prediction I need data. To get data I perhaps need a |
33 |
> > prediction. Which needs data. So at the moment I don't know what to do. |
34 |
> > |
35 |
> > One part I have finished right now, I can get the compile times from the |
36 |
> > emerge.log and submit it to a central database (see |
37 |
> > http://ripat.xs4all.nl). Some "basic" querying I can do too. |
38 |
> > |
39 |
> > My questions to you is: |
40 |
> > - would this be a nice feature to have? |
41 |
> > - would you be willing to provide me with compile time statistics? |
42 |
> > - do you have any hints / ideas what I can do to get this from a no |
43 |
> > dataless project to a data having project? |
44 |
> > |
45 |
> > Thanks, |
46 |
> > |
47 |
> > |
48 |
> > Rutger Lubbers |
49 |
> > |
50 |
> > |
51 |
> > -- |
52 |
> > gentoo-dev@g.o mailing list |
53 |
|
54 |
- -- |
55 |
Werner,- |
56 |
-----BEGIN PGP SIGNATURE----- |
57 |
Version: GnuPG v1.2.2 (GNU/Linux) |
58 |
|
59 |
iD8DBQE/IXxZxiU3uL/NdUYRAsAAAJ9wW5Euyazi7SAHeXi8ZXClQQG2ewCgjMHU |
60 |
WQ//loK+G6T/DpBToJF0gPI= |
61 |
=bWGf |
62 |
-----END PGP SIGNATURE----- |
63 |
|
64 |
|
65 |
-- |
66 |
gentoo-dev@g.o mailing list |