| 1 |
On 19-04-2008 11:35:24 -0500, Jeremy wrote: |
| 2 |
> Fabian Groffen wrote: |
| 3 |
> <snip> |
| 4 |
>> There is one thing that I don't quite like: |
| 5 |
>> switching from arch to ~arch means after `emerge -e system` nearly any |
| 6 |
>> system package needs to be updated, that is quite a shame |
| 7 |
> |
| 8 |
> This has to be done with a normal gentoo installation anyway. I think it is |
| 9 |
> a small concern if any at all! |
| 10 |
|
| 11 |
Normal Gentoo installations have the intention to remain arch, not to be |
| 12 |
switched to ~arch. Besides they start stage 3, so they don't compile as |
| 13 |
much as we do. |
| 14 |
|
| 15 |
>> Questioni is now how are we going to implement this, if we all agree |
| 16 |
>> this is the way to go? Do we agree in the first place? |
| 17 |
> |
| 18 |
> Will it be more or less work for the prefix devs? If we implement this |
| 19 |
|
| 20 |
More work, for sure. But the payoff hopefully is less work on |
| 21 |
debugging/checking bootstrap failures. |
| 22 |
|
| 23 |
> design but it is more work to do...is it really beneficial? will it |
| 24 |
> actually get done? Also, I think that the docs will stay more current which |
| 25 |
|
| 26 |
The system set is limited, and I expect stable keyword changes there to |
| 27 |
be very rare. That also means the bootstrap image has to change only |
| 28 |
every once in a while. Probably to bump the bootstrapped Portage |
| 29 |
version. |
| 30 |
|
| 31 |
> means less work there. We need to define a process to update stable |
| 32 |
> keywords. Maybe we can follow gentoo-x86 automagically on that one..but if |
| 33 |
|
| 34 |
Out of the question. What's stable for gentoo-x86 sometimes breaks for |
| 35 |
us. We simply have much more diversity, so it'll be more a one time job |
| 36 |
to set the stable keywords, do a check by bootstrapping and leaving it |
| 37 |
that way. |
| 38 |
|
| 39 |
> we do, then the docs will get out of date again, because the process hasn't |
| 40 |
> really changed. If system packages go stable automatically that is the same |
| 41 |
> as what we have now. |
| 42 |
|
| 43 |
Yes, introducing stable keywords means a lot of changes to docs and |
| 44 |
scripts because suddenly stable keywords are allowed and supposed to be |
| 45 |
retained. |
| 46 |
|
| 47 |
> The proposal needs some serious thought. However, I think it has potential |
| 48 |
> and I like it. |
| 49 |
|
| 50 |
An alternative would be a bootstrap image maintained as a "branch", but |
| 51 |
I don't know how to get people upgraded easily from there. Probably |
| 52 |
rsync would be a way out there too... but *sigh* we don't have rsync. |
| 53 |
|
| 54 |
|
| 55 |
-- |
| 56 |
Fabian Groffen |
| 57 |
Gentoo on a different level |
| 58 |
-- |
| 59 |
gentoo-alt@l.g.o mailing list |
Archives