1 |
> > <snip> |
2 |
> Now I understand. I think it is not necessary to provide all possible |
3 |
> USE-flag combinations (PHP alone would use more space than you |
4 |
> projected, I think). |
5 |
It is certainly infeasible either way to provide any large quantity of |
6 |
combinations from one central server, not unless someone donates a really |
7 |
impressive cluster with a really large SAN which I don't see happening any |
8 |
time soon. |
9 |
Even with the p2p idea compiling every single package with every single use |
10 |
flag is probably way out of reach, but this is unnecessary the p2p idea |
11 |
doesn't strive to have packages for absolutely everything but rather just to |
12 |
collect packages for everything that people HAVE compiled in order to avoid |
13 |
unnecessary replication by other people. |
14 |
> We should take some defaults (maybe 4-5 possible |
15 |
> combinations of USE-flags) and, as i said, lots of packages don't have |
16 |
> certain USE-flags and need only be compiled once for all our defaults. |
17 |
This defies the entire spirit of use flags as it will mean there are only |
18 |
binaries available if you use a specific set of use flags, at this point you |
19 |
lose any benefit Gentoo has over a normal binary distribution. |
20 |
Yes it would be better then nothing but it would not change the fact that many |
21 |
people will have to recompile the exact same thing that many other people are |
22 |
recompiling, which is the entire problem my idea is trying to address. |
23 |
It would be very nice to have something like this as part of the p2p binary |
24 |
idea, but to suggest this as a replacement for the idea is missing the point |
25 |
in my opinion. |
26 |
Anyway I guess we differ on this so there is no point arguing further in |
27 |
circles on it. |
28 |
> > But you only have packages for one set of USE flags, as portage does |
29 |
> > not currently store packages for different USE flags. |
30 |
> > Unless you are implying that the majority of users all have the same |
31 |
> > CFLAGS/Use flags and Programs as you it is unlikely that your 6 GB |
32 |
> > set would be anywhere near close to being able to provide usable |
33 |
> > binaries for many people. |
34 |
> This is where cooperation with the stats project would be really great. |
35 |
As I mention at the end of the email having statistics could help, but I |
36 |
suspect you will find that there are many different use flag combinations and |
37 |
that not enough people use the same identical use flags that compiling |
38 |
binaries for only that set of use flags would be sufficient for a large |
39 |
portion of Gentoo users to be able to use binaries. |
40 |
> > Sure even having the basic stuff available is a nice *start* but |
41 |
> > where are they going to be hosted and who is going to compile them, |
42 |
> > and using what server? |
43 |
> I think that could be managed. If you only build a subset and not all |
44 |
> USE-flag combinations, maybe someone could donate some VM. |
45 |
That is quite a big maybe, I am not prepared to work on something that relies |
46 |
on a possible donation that may never materialize. I would rather work on |
47 |
something like my idea that can start without any donation and then make use |
48 |
of donations as they become available, I find that people are far more likely |
49 |
to donate to something that already works personally. |
50 |
> > I am not sure what you mean here by not building everything again? |
51 |
> Maybe you have some different USE-flag profiles, let's say, kde and |
52 |
> gnome (enabling the needed flags, disabling the ones for the other |
53 |
> desktop environment). Then you only need to provide one binary package |
54 |
> for openssh, because it is not affected by the USE-flag differences. |
55 |
However how is this going to help people who want openssh to have kerberos |
56 |
support when kerberos is disabled in both of those profiles? This will only |
57 |
allow people to use binaries in some lucky cases and then force them back into |
58 |
compiling the instant they want to do something different. In fact this will |
59 |
act as an incentive not to do anything different which is the exact opposite |
60 |
of what Gentoo means to me. |
61 |
|
62 |
The whole point of the p2p idea is that there are already people out there |
63 |
compiling all of these things every day, and that if that work can be |
64 |
collected others can be saved from having to repeat the same process(If they |
65 |
are lucky enough to be using the same flags as someone before them, if not |
66 |
then they can donate there work and save others that come after them) |
67 |
No extra work is required other then tracking what people have compiled and |
68 |
sharing it in some way, and some security measures of course. |
69 |
Furthermore no statistics are even required as the idea is self regulating, if |
70 |
a use flag combination is popular then a package will already be available for |
71 |
it from someone else, if it is not popular then it won't be available. |
72 |
There are nice ways to improve this somewhat in the long run if some kind |
73 |
person does magically decide to donate some decent hardware, such as using |
74 |
that hardware to pre-generate binaries for popular packages and use flag |
75 |
combinations based on statistics without any user involvement, but in the |
76 |
meantime this can already be started with absolutely no hardware. |