| 1 |
>>>>> On Tue, 02 Mar 2021, Michael Orlitzky wrote: |
| 2 |
|
| 3 |
>> Are you volunteering to fix all the tools to support the new format |
| 4 |
>> correctly? |
| 5 |
|
| 6 |
> The PMS says that KEYWORDS is whitespace-separated. Probably only |
| 7 |
> repoman/pkgcheck would require trivial changes. |
| 8 |
|
| 9 |
No, there are other tools as well, e.g. ekeyword and ebuild-mode. |
| 10 |
|
| 11 |
As matter of fact, ebuild-mode accepts any ASCII whitespace characters |
| 12 |
(horizontal tab, new line, vertical tab, form feed, carriage return, |
| 13 |
and space) in KEYWORDS, but will change the line to its canonical format |
| 14 |
whenever a keyword is updated. That is, in correct order and with single |
| 15 |
spaces as separators. |
| 16 |
|
| 17 |
BTW, do package managers allow any Unicode whitespace (like "" ZERO |
| 18 |
WIDTH SPACE or " " OGHAM SPACE MARK) in places where PMS says |
| 19 |
"whitespace"? |
| 20 |
|
| 21 |
Ulrich |
Archives