1 |
Rich Freeman posted on Fri, 01 Jul 2011 16:50:28 -0400 as excerpted: |
2 |
|
3 |
> I wonder if there is a way to get around keeping cruft in the tree for |
4 |
> the sake of those who don't update often. |
5 |
> |
6 |
> Something that comes to mind is having a binpkg repository for |
7 |
> everything in system - essentially a binpkg stage3. |
8 |
|
9 |
Useful idea. |
10 |
|
11 |
One thing to keep in mind when we're talking about the download of |
12 |
historical binaries is the obligations of the GPL, etc, in that regard. |
13 |
Gentoo doesn't normally have to worry about this as it normally ships |
14 |
sources, not binaries, and for current stage tarballs, which /are/ |
15 |
binary, the sources are, pretty much by definition as Gentoo handles it, |
16 |
made available at the same time (tho there might possibly be argument |
17 |
over whether they're made available at the same place, etc, I've made no |
18 |
attempt to grok or verify the legal minutia in that regard). |
19 |
|
20 |
But once you start shipping historical binaries, as we're talking here, |
21 |
we need to worry about EITHER keeping sources available at the same time/ |
22 |
place for them too, as long as they're shipped, OR keeping them available |
23 |
to be shipped upon request to ANYONE for up to three years. Based on |
24 |
previous discussion, the make available at the same time and place clause |
25 |
is considered easier for distributions such as Gentoo to fulfill than the |
26 |
upon request for three years clause. |
27 |
|
28 |
(That's the GPLv2 requirements as I understand them. I don't understand |
29 |
the GPLv3 and its differences in that regard really at all... except that |
30 |
I believe the same basic idea remains valid. IANAL. The Gentoo |
31 |
Foundation folks are the ones who probably should be tracking this. |
32 |
Etc...) |
33 |
|
34 |
This discussion came up at least once before, some years ago, when Gentoo |
35 |
was still making available historic stage tarballs dating back to 1.4 or |
36 |
earlier, and there was some real question as to whether we were sure that |
37 |
all the required sources were still available. I never validated whether |
38 |
action was actually taken, but the conclusion from that discussion, IIRC, |
39 |
was that the best practical action we could take would be to (1) ensure |
40 |
that we always kept corresponding sources from then on and made them |
41 |
available at the same time/place as the binaries, and (2), quit |
42 |
distributing the "historic interest" stages that there was a legitimate |
43 |
question about as to whether we could provide sources or not. |
44 |
|
45 |
Just something to keep in mind any time the idea of public availability |
46 |
of non-current binaries, for whatever reason, comes up. It's not all |
47 |
purely technical worries, tho fortunately, implementation of the legal |
48 |
requirements does ultimately boil down to technical details, too. |
49 |
|
50 |
I'd opine that's one practical reason why binaries remain a definite |
51 |
secondary from Gentoo's perspective -- sources-only lessens the legal |
52 |
requirements DRAMATICALLY, both as regards the GPL, and in regard to |
53 |
patents. |
54 |
|
55 |
Hopefully that's not a discouragement for something that I really believe |
56 |
is a great idea, but it /does/ need to be considered. |
57 |
|
58 |
-- |
59 |
Duncan - List replies preferred. No HTML msgs. |
60 |
"Every nonfree program has a lord, a master -- |
61 |
and if you use the program, he is your master." Richard Stallman |