| 1 |
Christian Faulhammer <opfer@g.o> posted |
| 2 |
20081022172853.41878802@×××××.solaris, excerpted below, on Wed, 22 Oct |
| 3 |
2008 17:28:53 +0200: |
| 4 |
|
| 5 |
> no support in stable profile out-of-the-box -> no stable keyword -> |
| 6 |
> INVALID request. No compromise. |
| 7 |
|
| 8 |
Well, at least the one referenced bug (243050) is for an ~arch keyword, |
| 9 |
not a stable keyword. That's different, as the ~arch keyword is useful |
| 10 |
for saying yes, it has been tested and is known to be workable on that |
| 11 |
particular arch in /some/ form, even if it's not (and may never be) |
| 12 |
stable. x86 many not have to worry about that, but the other archs do. |
| 13 |
|
| 14 |
But mentioning that it can never be stabilized (and referring to a policy |
| 15 |
URL for why) in the package description would still be good, as would |
| 16 |
mention of the fact that yes, it does require user application of patches |
| 17 |
elsewhere. |
| 18 |
|
| 19 |
-- |
| 20 |
Duncan - List replies preferred. No HTML msgs. |
| 21 |
"Every nonfree program has a lord, a master -- |
| 22 |
and if you use the program, he is your master." Richard Stallman |
Archives