| 1 |
>>>>> On Thu, 14 Jan 2016, Michał Górny wrote: |
| 2 |
|
| 3 |
> On Thu, 14 Jan 2016 07:28:43 -0500 |
| 4 |
> Rich Freeman <rich0@g.o> wrote: |
| 5 |
|
| 6 |
>> One way to do this (and I'm certainly open to others) is a |
| 7 |
>> Display-If-Installable header which takes a keyword string and an |
| 8 |
>> atom (typically a specific PV). The package manager would |
| 9 |
>> determine if a package with that keyword string and PV would be |
| 10 |
>> accepted or not based on the user's configuration, and if so |
| 11 |
>> display the news. |
| 12 |
|
| 13 |
> Based on your idea, this is how I'd do it: |
| 14 |
|
| 15 |
> 1. 'Display-If-Visible' that enables news items if given atom is |
| 16 |
> visible for PM (i.e. in repo, with right keywords and not masked). |
| 17 |
> I would avoid using 'Installable' as that could get confusing wrt |
| 18 |
> conflicts and so on. |
| 19 |
|
| 20 |
I had omitted the Display-If-Visible header (which has been discussed |
| 21 |
since 2007 at least) deliberately, because we want to get format 2.0 |
| 22 |
done in a timely manner. |
| 23 |
|
| 24 |
The problem with any visibility filtering is that visibility depends |
| 25 |
on user configuration [1], and I don't know what changes in the |
| 26 |
package manager would be necessary to make this work correctly and |
| 27 |
efficiently. For example, how does portage's --autounmask-write option |
| 28 |
interact with it? |
| 29 |
|
| 30 |
Ulrich |
| 31 |
|
| 32 |
[1] https://bugs.gentoo.org/show_bug.cgi?id=290038#c9 |
Archives