| 1 |
Wernfried Haas wrote: |
| 2 |
|
| 3 |
>On Wed, Nov 30, 2005 at 01:56:40PM -0500, Mark Loeser wrote: |
| 4 |
> |
| 5 |
> |
| 6 |
>>Seems people read this to mean that I was going to write a doc, which I have |
| 7 |
>>no intentions on doing. |
| 8 |
>> |
| 9 |
>> |
| 10 |
>I don't think a whole doc is necessary, but instructions for a safe |
| 11 |
>upgrade would be fine. A think a one-liner like |
| 12 |
>emerge -u gcc && emerge -e system && emerge -e world && emerge -P gcc |
| 13 |
>&& emerge whateverneedstobedoneafterwards should suffice as documentation. |
| 14 |
> |
| 15 |
> |
| 16 |
> |
| 17 |
>>I believe adding "It is recommended that you `emerge |
| 18 |
>>-e system && emerge -e world` after merging gcc-3.4" to the einfo at the end |
| 19 |
>>of the gcc-3.4.4 install should be good enough. |
| 20 |
>> |
| 21 |
>> |
| 22 |
>Maybe people look closer if they upgrade gcc, but einfo still gets |
| 23 |
>overlooked easily. |
| 24 |
> |
| 25 |
> |
| 26 |
> |
| 27 |
>>So, let me know if marking it stable in the next day or two is completely |
| 28 |
>>stupid and I should wait to announce this via the GWN or something, or if its |
| 29 |
>>an alright move and people aren't going to stab me for marking it stable. |
| 30 |
>> |
| 31 |
>> |
| 32 |
>Assuming a clear upgrade path is provided i think it would be |
| 33 |
>fine. We'll make some sticky thread on the forum mentioning that |
| 34 |
>instructions, i bet it couldn't hurt to put them on the gentoo |
| 35 |
>mainpage, as topic in #gentoo etc. I'm also pretty sure next GWN is |
| 36 |
>likely to report about the update. |
| 37 |
>Just because we haven't got emerge --news it doesn't mean we haven't |
| 38 |
>got lots of ways to reach our users. Every user that gets to read them |
| 39 |
>in time is a potential bug report less. |
| 40 |
> |
| 41 |
>cheers, |
| 42 |
> Wernfried |
| 43 |
> |
| 44 |
> |
| 45 |
Personally, I would set a date next week, so that way GWN and other |
| 46 |
places can be prepare for this, a definate date for users to know that |
| 47 |
it IS going to happen, and I personally think that a sticky on the forum |
| 48 |
(i would even be willing to write a little something, but i'm no expert) |
| 49 |
is a minimum. A full out doc with all the FAQ and important notes about |
| 50 |
what needs to be recompiled (in my opinion) would be a much more through |
| 51 |
upgrade path, ofcourse still include the einfo quick instructions. But I |
| 52 |
think the masses of users will not be happy when they realize that |
| 53 |
emerge -e world && emerge -e world means that they will be compiling for |
| 54 |
the next day (or 2 or 3), so a way to block the upgrade from messing up |
| 55 |
people that wish to keep 3.3.x as default would be a good idea. |
| 56 |
|
| 57 |
just my $.02 |
| 58 |
|
| 59 |
Tux |
| 60 |
-- |
| 61 |
gentoo-dev@g.o mailing list |
Archives