1 |
I understand guys and I think you are doing a great job. I've |
2 |
personally used Linux since the end of 1994, started off with |
3 |
Slackware but during the later years been using various dists of BSD |
4 |
instead. However, I recently found the joy in Gentoo and have now been |
5 |
using it for the last 6 months on a number of servers and other |
6 |
machines. Just want to give my input and i really appreciate the |
7 |
response I've been given here. Keep up the good work guys! |
8 |
|
9 |
On 5/11/06, Chris Gianelloni <wolf31o2@g.o> wrote: |
10 |
> On Thu, 2006-05-11 at 19:39 +0200, George Hedfors wrote: |
11 |
> > Well no, but I did this change before doing the actual bootstrap. I |
12 |
> > followed the quick install guide and made changes to make.conf, then |
13 |
> > completed bootstrap.sh and started emerging the system. Thats when it |
14 |
> > happend. As there is a stage-installed perl version, when the library |
15 |
> > tried to compile, it used the present perl version as it was dependent |
16 |
> > on it. However, as the stage-installed version did'nt work with my |
17 |
> > changes, i had to manually upgrade perl before i could emerge the rest |
18 |
> > of the system. I'm sure other people will have the same problem and to |
19 |
> > solve this, one way would be to reinstall perl somewhere in the very |
20 |
> > beguinning of emerge system. |
21 |
> > |
22 |
> > I'm just a stupid user trying to make life easier for others :). |
23 |
> |
24 |
> While I understand and we truly do appreciate the input, this is |
25 |
> *exactly* why Release Engineering has dropped support for stage1 and |
26 |
> stage2 installs and recommend to everyone to use the stage3 tarballs for |
27 |
> *all* installations. |
28 |
> |
29 |
> The stage3 tarball is a known-good minimal working system. |
30 |
> |
31 |
> There are simply too many variables possible in doing a stage1 or stage2 |
32 |
> installation that need to be addressed. I honestly should change the |
33 |
> end bootstrap.sh message to tell the user that if something breaks, they |
34 |
> get to pick up the pieces themselves. ;] |
35 |
> |
36 |
> Gentoo has, unfortunately, become a victim of its own success. The more |
37 |
> flexibility we add to the system, the harder it is to test for multiple |
38 |
> scenarios that are possible when doing an installation. For some time |
39 |
> now, it has been simply impossible for us to test stage1 and stage2 |
40 |
> installations with any degree of certainty that what builds on my |
41 |
> machine will build on yours. There's simply too many USE flags |
42 |
> affecting the "system" target. Also, most people don't realize that |
43 |
> "system" is 100% contrived by portage from the profile and its own |
44 |
> internal dependency calculations. We simply can't make something appear |
45 |
> sooner in the dependency tree than it already does, without editing the |
46 |
> ebuilds, which almost always has unforseen consequences, causing a |
47 |
> back-out. |
48 |
> |
49 |
> Trust me. This is exactly what takes us so long during releases to get |
50 |
> going. It usually takes us a few weeks just to get the stages to build |
51 |
> properly, due to changes that have happened in the tree since the last |
52 |
> release. |
53 |
> |
54 |
> If you want an installation that actually *works*, use a stage3 tarball. |
55 |
> If you're familiar with the concepts of bootstrapping and are |
56 |
> comfortable with cleaning up after portage vomiting all over your system |
57 |
> because of something that changed in the time since release and you |
58 |
> doing your installation, feel free to use the lower stages. Personally, |
59 |
> I *always* use a stage3 installation now. Most of the time, I use GRP. |
60 |
> I hate waiting to get a usable system. I'd much rather be checking my |
61 |
> email and letting a compile go on in the background than stare at a |
62 |
> console of scrolling text and not be able to do much but ssh to another |
63 |
> box or chat on IRC for days. |
64 |
> |
65 |
> -- |
66 |
> Chris Gianelloni |
67 |
> Release Engineering - Strategic Lead |
68 |
> x86 Architecture Team |
69 |
> Games - Developer |
70 |
> Gentoo Linux |
71 |
> |
72 |
> |
73 |
> -----BEGIN PGP SIGNATURE----- |
74 |
> Version: GnuPG v1.4.3 (GNU/Linux) |
75 |
> |
76 |
> iD8DBQBEY6cikT4lNIS36YERAny5AJ4+UusF/DLMqrXE89+weO553GwOAACffEM2 |
77 |
> ys4evBo0BhI1p4xKSq0mH8c= |
78 |
> =XEFZ |
79 |
> -----END PGP SIGNATURE----- |
80 |
> |
81 |
> |
82 |
> |
83 |
|
84 |
|
85 |
-- |
86 |
PGP Fingerprint: |
87 |
4BB9 7A99 3DB5 52AA 8CEF 4DFB 32F2 41AC 0EF2 D595 |
88 |
|
89 |
-- |
90 |
gentoo-doc@g.o mailing list |