| 1 |
Am Samstag, 6. Mai 2017, 18:35:08 CEST schrieb Michał Górny: |
| 2 |
> |
| 3 |
> > An implementation is still missing though. |
| 4 |
> |
| 5 |
> ...and a rationale section to describe why you did the things this way. |
| 6 |
|
| 7 |
Well, that's more or less the Motivation section. Should I rename it? |
| 8 |
|
| 9 |
> 1. I think your example is a bit misleading -- unless I'm missing |
| 10 |
> something, mips would be 'unstable' right now, and m68k would be |
| 11 |
> 'testing'. |
| 12 |
|
| 13 |
Right. Fixed. |
| 14 |
|
| 15 |
> 2. I can't say I like using magical keywords like 'testing' |
| 16 |
> and 'unstable'; they're going to be confusing long-term (compare: |
| 17 |
> the mess with stable/exp/dev for profiles). But I don't have a very good |
| 18 |
> idea how to it better right now. |
| 19 |
|
| 20 |
Well, I pulled the two terms that are tradidionally used for ~arch... |
| 21 |
"testing" and "unstable". Testing implied to me that a transition is taking |
| 22 |
place, so that went to the "mixed state". |
| 23 |
|
| 24 |
There's also Kent's proposal where some more indirection is introduced (see |
| 25 |
the discussion threads). It more or less achives the same with even more |
| 26 |
flexibility. I dont like it so much because I want to keep things simple. |
| 27 |
|
| 28 |
> 3. What is the use case for 'broken'? Are we ever going to use that? |
| 29 |
|
| 30 |
None that I know of. I only added it because it was suggested on the list (and |
| 31 |
because it's simple to define and implement). |
| 32 |
|
| 33 |
> |
| 34 |
> Plus, you have a few typos, you need to wikify it and other minor blah |
| 35 |
> blah. |
| 36 |
|
| 37 |
|
| 38 |
-- |
| 39 |
Andreas K. Hüttel |
| 40 |
dilfridge@g.o |
| 41 |
Gentoo Linux developer (council, perl, libreoffice) |
Archives