| 1 |
Samuli Suominen posted on Fri, 29 Mar 2013 10:09:27 +0200 as excerpted: |
| 2 |
|
| 3 |
> This feature will also replace the functionality of sys-apps/biosdevname |
| 4 |
> which you should uninstall. However, you can still keep using |
| 5 |
> sys-apps/biosdevname if you want. |
| 6 |
|
| 7 |
I'd suggest... |
| 8 |
|
| 9 |
This feature can optionally replace... can uninstall. |
| 10 |
|
| 11 |
IOW... |
| 12 |
|
| 13 |
s/will also/can optionally/ |
| 14 |
|
| 15 |
s/should/can/ |
| 16 |
|
| 17 |
|
| 18 |
It sounds less menacing than your suggested wording, making it clearer |
| 19 |
that it's an optional replacement and lessening the apparent conflict and |
| 20 |
possible confusion with the next sentence saying it can still be used if |
| 21 |
desired. |
| 22 |
|
| 23 |
I'd say that's a particularly good idea given the sensitivity around the |
| 24 |
"all engulfing gray goo" that systemd has seemed to many to have become. |
| 25 |
Given that upstream specifically designed this feature to cooperate with |
| 26 |
existing biosdevname installations, let's not unnecessarily poke that |
| 27 |
hornet's nest by implying otherwise, even if the next sentence /does/ |
| 28 |
basically say it's an optional change anyway. =:^/ |
| 29 |
|
| 30 |
-- |
| 31 |
Duncan - List replies preferred. No HTML msgs. |
| 32 |
"Every nonfree program has a lord, a master -- |
| 33 |
and if you use the program, he is your master." Richard Stallman |
Archives