From: Ciaran McCreesh <ciaran.mccreesh@googlemail.com>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Re: Deleting old news items
Date: Sat, 6 Jan 2018 16:25:36 +0000 [thread overview]
Message-ID: <20180106162536.43951d3a@snowtea> (raw)
In-Reply-To: <b96624ba-478f-b9bb-d0cf-3152709fe477@gmail.com>
On Sat, 6 Jan 2018 08:18:19 -0500
kuzetsa <kuzetsa@gmail.com> wrote:
> On 01/06/2018 05:05 AM, Ulrich Mueller wrote:
> >>>>>> On Sat, 6 Jan 2018, Duncan wrote:
> >> $ equery b news.eselect
> >> app-admin/eselect-1.4.10 (/usr/share/eselect/modules/news.eselect)
> >> So in that case it's not the PM, but eselect.
> > In fact, it is the PM that would do the filtering, before filling
> > the list of unread news items
> > in /var/lib/gentoo/news/news-gentoo.read.
> >
> > Filtering in eselect news would be problematic: Obtaining the list
> > of items with "eselect news list" and e.g. reading them with
> > "eselect news read" are issued as separate commands, which requires
> > that the list of valid items does not change. However, time-based
> > filtering could cause a race condition, like an item expiring
> > between execution of the two commands.
>
> The race condition could be addressed by issuing a warning
> at or around the time when expirations occur (midnight),
> with or without detecting specific expirations which may
> have occurred:
How accurate is "around"? Obviously we'd need to introduce a user
configuration option so different users could set appropriate values
for their needs.
Seriously though, all this complexity is just highlighting that dates
are a really bad way of deciding when a news item should expire, and
that if we need anything, it's more Display-If conditions.
--
Ciaran McCreesh
next prev parent reply other threads:[~2018-01-06 16:25 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-03 0:13 [gentoo-dev] Deleting old news items Alec Warner
2018-01-03 0:17 ` Mikle Kolyada
2018-01-03 1:14 ` Aaron W. Swenson
2018-01-03 10:35 ` [gentoo-dev] " Michael Palimaka
2018-01-03 10:53 ` [gentoo-dev] " Michał Górny
2018-01-03 11:00 ` kuzetsa
2018-01-03 11:07 ` Ulrich Mueller
2018-01-03 11:22 ` kuzetsa
2018-01-03 11:23 ` Kristian Fiskerstrand
2018-01-03 13:45 ` Ciaran McCreesh
2018-01-03 14:13 ` Kristian Fiskerstrand
2018-01-03 14:18 ` Kristian Fiskerstrand
2018-01-03 15:16 ` Alec Warner
2018-01-05 1:20 ` Alec Warner
2018-01-05 3:01 ` Alec Warner
2018-01-05 10:08 ` Ulrich Mueller
2018-01-05 14:01 ` Alec Warner
2018-01-05 21:16 ` William Hubbs
2018-01-05 21:28 ` Aaron W. Swenson
2018-01-05 22:09 ` Kristian Fiskerstrand
2018-01-05 22:40 ` Alec Warner
2018-01-05 22:47 ` Kristian Fiskerstrand
2018-01-05 22:53 ` Kristian Fiskerstrand
2018-01-05 23:55 ` Michał Górny
2018-01-06 1:59 ` Alec Warner
2018-01-06 8:30 ` [gentoo-dev] " Duncan
2018-01-06 10:05 ` Ulrich Mueller
2018-01-06 13:18 ` kuzetsa
2018-01-06 16:25 ` Ciaran McCreesh [this message]
2018-01-06 18:13 ` Alec Warner
2018-01-06 19:51 ` Anders Thomson
2018-01-06 20:30 ` Alec Warner
2018-01-06 22:11 ` Anders Thomson
2018-01-06 22:13 ` Kristian Fiskerstrand
2018-01-07 18:50 ` Denis Lisov
2018-01-05 9:00 ` [gentoo-dev] " Michał Górny
2018-01-05 14:07 ` Alec Warner
2018-01-05 10:15 ` nado
2018-01-05 14:01 ` Alec Warner
2018-01-05 14:08 ` Alec Warner
2018-01-05 15:23 ` Ulrich Mueller
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20180106162536.43951d3a@snowtea \
--to=ciaran.mccreesh@googlemail.com \
--cc=gentoo-dev@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox