1 |
On Fri, Jul 1, 2011 at 5:39 PM, Duncan <1i5t5.duncan@×××.net> wrote: |
2 |
> One thing to keep in mind when we're talking about the download of |
3 |
> historical binaries is the obligations of the GPL, etc, in that regard. |
4 |
>... |
5 |
> But once you start shipping historical binaries, as we're talking here, |
6 |
|
7 |
Actually, I wasn't thinking about providing historical binaries - just |
8 |
ones matching those in a stage3. Binary distribution of stage3 is a |
9 |
problem we already have license-wise. |
10 |
|
11 |
The problem with just unzipping a stage3 on your system is that you |
12 |
break all the package management tracking of files. The solution I'm |
13 |
proposing is to just use a binary emerge to do the exact same thing |
14 |
(perhaps selectively) so that everything is package managed. |
15 |
|
16 |
Now, this will still break anything that has an RDEPEND on a system |
17 |
package with a non-standard use flag. I suspect those kinds of issues |
18 |
are going to be relatively rare. Also, they're easily fixed. |
19 |
|
20 |
The real big problem with an emerge -uD world on a system that is a |
21 |
year old is that the toolchain and other key system packages may not |
22 |
be able to update themselves all in one shot. Maybe the new portage |
23 |
doesn't run on the old python, or you have some kind of circular |
24 |
situation where two toolchain packages don't build with the other's |
25 |
old version. |
26 |
|
27 |
Using a binary repository would let you get a USE-neutral clean copy |
28 |
of any of that stuff installed. There are still things that could go |
29 |
wrong (mostly related to fetching/extraction/python/portage), but the |
30 |
number of components that need to be working for a binary install is |
31 |
much lower than for a full build. So, I would think that it is pretty |
32 |
likely that you could jump straight to a modern system if you did a |
33 |
binary emerge. Then you could do a revdep-rebuild, or even an emerge |
34 |
-e system/world to really clean things up. |
35 |
|
36 |
Maybe there is some obvious flaw in my logic here... |
37 |
|
38 |
Rich |