1 |
> Sure, it sounds good, but will it ever get off the ground? |
2 |
> I'm not convinced that this idea will take off... |
3 |
|
4 |
OK, we were talking about "GRP" -- the official, current definition here, |
5 |
which is already off the ground, clearly works, and used by lots of people. |
6 |
Several years ago, many Gentoo developers were against GRP as it exists |
7 |
today, and it was a large uphill battle to push for the creation of binary |
8 |
packages. What we are talking about is whether a possibility exists for |
9 |
Gentoo to totally regress to that original state, with next to no pre-built |
10 |
packages were available for our users. At this point, as Sven points out, |
11 |
there would be a great amount of resistance to GRP being dropped entirely |
12 |
(many users rely on GRP, the installer project is going strong, etc.) |
13 |
|
14 |
The stuff in GLEP 26 should be called something else, since it seems like |
15 |
we're all getting confused about what everyone else is talking about. And I |
16 |
agree with you in that it may not get off the ground any time soon. This |
17 |
shouldn't prevent interested parties in trying to figure out how to get it |
18 |
("it" being binary packages to keep your system up-to-date) to work, though. |
19 |
And I can certainly understand why infrastructure may not want to host a |
20 |
comprehensive binary package update repository, since that could potentially |
21 |
involve a huge commitment of both CPU and storage resources. So huge, in |
22 |
fact, that it may be technically impossible to do as an official effort |
23 |
under the Gentoo Foundation itself. |
24 |
|
25 |
But I think the incremental binary update _technology_ is worth having. A |
26 |
lot of companies and educational institutions are trying to figure out how |
27 |
to deploy Gentoo and keep all their machines up-to-date. If incremental |
28 |
binary package updates are an option for them, I'm sure they'd appreciate |
29 |
it. Now, I am not saying that _we_ would provide the binary packages to |
30 |
them. We don't need to host the binary packages -- Gentoo can simply create |
31 |
the technology, explain how to use it, and then interested companies and |
32 |
universities can build their own package sets for their own internal use. |
33 |
Then they have a very efficient way to keep their catalyst-built Gentoo |
34 |
systems up-to-date. |
35 |
|
36 |
I bet that a handful will make their binary packages available to the |
37 |
public. For some organizations, this would be appealing because additional |
38 |
users would result in more QA over time, more bug reports, and the ability |
39 |
to improve their binary package sets faster. I think that this is more |
40 |
likely to happen in an academic setting, though. |
41 |
|
42 |
Just some ideas... |
43 |
|
44 |
Regards, |
45 |
|
46 |
Daniel |
47 |
|
48 |
|
49 |
-- |
50 |
gentoo-releng@g.o mailing list |