| 1 |
On 10/31/05, Chris Gianelloni <wolf31o2@g.o> wrote: |
| 2 |
> |
| 3 |
> As it stands, I only see a few options, none of which sound very good: |
| 4 |
> |
| 5 |
> 1. Only release stage3 tarballs |
| 6 |
|
| 7 |
|
| 8 |
This is the worst of all these options. I for one have never done a stage3 |
| 9 |
install and never plan/want to. I am pretty sure there are others out there |
| 10 |
like me that would be extremely ticked off to see our stage1 tarballs |
| 11 |
disappear. |
| 12 |
|
| 13 |
2. Inform users that only stage3 will be supported |
| 14 |
|
| 15 |
|
| 16 |
This may actually be your best route. Any bugs that come in because users |
| 17 |
customized use flags on a non-stage3 install should be closed RTFM. |
| 18 |
|
| 19 |
3. Change the documentation to recommend users not change USE flags |
| 20 |
> until after the completion of "emerge -e system" |
| 21 |
|
| 22 |
|
| 23 |
You could try this first but if people think they are smart enough to change |
| 24 |
the use flags (even if they really aren't) then there isn't much of a chance |
| 25 |
you're going to talk them out of it. |
| 26 |
|
| 27 |
I am not sure how the other (non-minimal) cd's are setup but you could just |
| 28 |
include stage3's on the cds and make people go out to the mirrors to get |
| 29 |
their stage1 or 2 tarballs. Basically make it a little bit more difficult to |
| 30 |
get them. |
| 31 |
|
| 32 |
Another thought would be an approach similar to the installer irc channel |
| 33 |
where you have to read through a really long FAQ before you are told how to |
| 34 |
download the stage1 or 2 tarballs. |
| 35 |
|
| 36 |
Just my thoughts as an end user. |
| 37 |
|
| 38 |
-Mike |
| 39 |
|
| 40 |
-- |
| 41 |
________________________________ |
| 42 |
Michael E. Crute |
| 43 |
Software Developer |
| 44 |
SoftGroup Development Corporation |
| 45 |
|
| 46 |
Linux, because reboots are for installing hardware. |
| 47 |
"In a world without walls and fences, who needs windows and gates?" |
Archives