| 1 |
In its last meeting the council has accepted an extension of the |
| 2 |
news item format which allows EAPI=5 style package dependency |
| 3 |
specifications. This has triggered a discussion if this change is |
| 4 |
backwards or forwards compatible, and what should be the new format's |
| 5 |
version number [1]. Also it is not entirely clear if the term |
| 6 |
"backwards-compatible" used in GLEP 42 correctly describes what was |
| 7 |
originally intended [2]. |
| 8 |
|
| 9 |
In any case, both portage [3] and paludis [4] will have to be updated |
| 10 |
for the new format because the change is not forwards-compatible. |
| 11 |
|
| 12 |
Therefore, we could use the opportunity to add some other features. |
| 13 |
So far, this includes: |
| 14 |
|
| 15 |
1. Display-If-Installed: Allow EAPI=5 style package dependency |
| 16 |
specifications (see above). |
| 17 |
|
| 18 |
2. Display-If-Profile: Allow wildcards like default-linux/* [5]. |
| 19 |
|
| 20 |
3. Title: Increase maximum length. In the past, devs repeatedly |
| 21 |
struggled with the current 44 character limit. (Can anyone |
| 22 |
enlighten me where this originates from? I cannot find anything in |
| 23 |
the discussions around the time when GLEP 42 was submitted.) |
| 24 |
The eselect news reader could still display a 51 character title |
| 25 |
in one line for the "list" and "read" commands, on an 80 character |
| 26 |
wide terminal. |
| 27 |
I suggest we round this down to a maximum length of 50 characters, |
| 28 |
which (together with the 72 character limit for the body) would |
| 29 |
nicely agree with the limits recommended for git commit messages. |
| 30 |
|
| 31 |
4. Content-Type: Only one value is allowed for this header, namely |
| 32 |
text/plain. We might as well drop it, because any changes there |
| 33 |
will require an increment of the News-Item-Format. |
| 34 |
|
| 35 |
If these changes find agreement, I would prepare a new GLEP for news |
| 36 |
item format 2.0. |
| 37 |
|
| 38 |
Ulrich |
| 39 |
|
| 40 |
|
| 41 |
[1] https://bugs.gentoo.org/show_bug.cgi?id=568068#c4 |
| 42 |
[2] https://archives.gentoo.org/gentoo-dev/message/d30de011db9067ae3cc298de2b4ee1b2 |
| 43 |
[3] https://gitweb.gentoo.org/proj/portage.git/tree/pym/portage/news.py?id=7c94014a32d173ae61919b762140ac1c32d3b522#n273 |
| 44 |
[4] http://git.exherbo.org/paludis/paludis.git/tree/paludis/repositories/e/e_repository_news.cc?id=1684b446715907515359cd310c1e7bd93bad5a2e#n326 |
| 45 |
[5] https://bugs.gentoo.org/show_bug.cgi?id=290038 |
Archives