| 1 |
On Sat, Jan 6, 2018 at 1:05 PM, Ulrich Mueller <ulm@g.o> wrote: |
| 2 |
> Filtering in eselect news would be problematic: Obtaining the list |
| 3 |
> of items with "eselect news list" and e.g. reading them with "eselect |
| 4 |
> news read" are issued as separate commands, which requires that the |
| 5 |
> list of valid items does not change. However, time-based filtering |
| 6 |
> could cause a race condition, like an item expiring between execution |
| 7 |
> of the two commands. |
| 8 |
|
| 9 |
Would it be possible to make the expiration times use not the wall |
| 10 |
clock time, but the timestamp of the repository if one is available? |
| 11 |
|
| 12 |
That would not only be more predictable (can expire on repository |
| 13 |
manipulations only), but also better suited for updating severely |
| 14 |
outdated systems. You can advance the repository state by 1 year and |
| 15 |
read the news items as they were at that time, not half of them |
| 16 |
expired and hidden. |
| 17 |
|
| 18 |
Denis Lisov. |
Archives