| 1 |
Many news items are only relevant when upgrading a package from one |
| 2 |
version to another. For fresh installs, the user does not need to take |
| 3 |
any action. A good example of this is the recent gcc upgrade from 4.9 |
| 4 |
to 5. |
| 5 |
|
| 6 |
In this context, it is often desirable to inform the user of a major |
| 7 |
change in a package before they upgrade it. This would give them time |
| 8 |
to prepare, and allow to skip the upgrade until they are ready. |
| 9 |
|
| 10 |
This is technically possible with the current news item format by |
| 11 |
using a Display-If-Installed header. However, this has a few problems |
| 12 |
depending on how you format the dependency spec. |
| 13 |
|
| 14 |
Display-If-Installed: cat/pkg |
| 15 |
This will be displayed to too many users. |
| 16 |
|
| 17 |
Display-If-Installed: >=cat/pkg-ver |
| 18 |
This will be displayed to users only after they have upgraded. |
| 19 |
|
| 20 |
Display-If-Installed: <cat/pkg-ver |
| 21 |
This targets the right people, but the message will be displayed too |
| 22 |
early for stable users. |
| 23 |
|
| 24 |
I would like to introduce a new header "Display-If-Visible". This |
| 25 |
would restrict display of the news item to users for which the given |
| 26 |
dependency is visible according to their ACCEPT_KEYWORDS and |
| 27 |
package.accept_keywords settings. |
| 28 |
|
| 29 |
Example usage: |
| 30 |
|
| 31 |
Display-If-Installed: <sys-devel/gcc-5 |
| 32 |
Display-If-Visible: >=sys-devel/gcc-5 |
| 33 |
|
| 34 |
Comments? |
Archives