| 1 |
Fabian Groffen wrote: |
| 2 |
<snip> |
| 3 |
> There is one thing that I don't quite like: |
| 4 |
> switching from arch to ~arch means after `emerge -e system` nearly any |
| 5 |
> system package needs to be updated, that is quite a shame |
| 6 |
|
| 7 |
This has to be done with a normal gentoo installation anyway. I think it |
| 8 |
is a small concern if any at all! |
| 9 |
|
| 10 |
> So the alternative is to switch from arch to ~arch in the post-sync |
| 11 |
> stage. Thoughts here? |
| 12 |
> |
| 13 |
> Questioni is now how are we going to implement this, if we all agree |
| 14 |
> this is the way to go? Do we agree in the first place? |
| 15 |
|
| 16 |
Will it be more or less work for the prefix devs? If we implement this |
| 17 |
design but it is more work to do...is it really beneficial? will it |
| 18 |
actually get done? Also, I think that the docs will stay more current |
| 19 |
which means less work there. We need to define a process to update |
| 20 |
stable keywords. Maybe we can follow gentoo-x86 automagically on that |
| 21 |
one..but if we do, then the docs will get out of date again, because the |
| 22 |
process hasn't really changed. If system packages go stable |
| 23 |
automatically that is the same as what we have now. |
| 24 |
|
| 25 |
The proposal needs some serious thought. However, I think it has |
| 26 |
potential and I like it. |
| 27 |
|
| 28 |
-Jeremy |
| 29 |
|
| 30 |
-- |
| 31 |
gentoo-alt@l.g.o mailing list |
Archives