From: Ciaran McCreesh <ciaranm@ciaranm.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] GLEP 42 news item for review: Radiant upgrade
Date: Sun, 6 May 2007 20:46:36 +0100 [thread overview]
Message-ID: <20070506204636.07564b1b@snowflake> (raw)
In-Reply-To: <463E2FDB.4020407@gentoo.org>
[-- Attachment #1: Type: text/plain, Size: 828 bytes --]
On Sun, 06 May 2007 21:43:23 +0200
Vlastimil Babka <caster@gentoo.org> wrote:
> Ciaran McCreesh wrote:
> >> My intention would be to show these right after 'emerge --sync' or
> >> 'emerge --pretend', not when the package is about to be merged.
> >
> > Then you want the non-existent pkg_pretend_post() feature, not GLEP
> > 42.
>
> glep 42:
>
> Checks for new news messages should be displayed:
>
> * After an emerge sync
> * After an emerge --pretend
> * Before an emerge <target> (which may also include a red warning
> message)
*sigh*
The messages wouldn't be marked as 'to be read' at any of those points
for the situation being discussed.
Again, try out a reference implementation if you're having trouble
understanding the system and its implications.
--
Ciaran McCreesh
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2007-05-06 19:52 UTC|newest]
Thread overview: 61+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-06 6:45 [gentoo-dev] GLEP 42 news item for review: Radiant upgrade Hans de Graaff
2007-05-06 8:48 ` Petteri Räty
2007-05-06 9:03 ` Petteri Räty
2007-05-06 10:05 ` Hans de Graaff
2007-05-06 10:34 ` Petteri Räty
2007-05-06 15:23 ` Dan Meltzer
2007-05-06 9:11 ` expose
2007-05-06 9:58 ` Maurice van der Pot
2007-05-06 15:33 ` Ciaran McCreesh
2007-05-06 15:49 ` Hans de Graaff
2007-05-06 15:51 ` Ciaran McCreesh
2007-05-06 16:20 ` expose
2007-05-06 16:27 ` Ciaran McCreesh
2007-05-06 17:16 ` Marius Mauch
2007-05-06 17:42 ` Ciaran McCreesh
2007-05-06 18:43 ` Hans de Graaff
2007-05-06 18:52 ` Ciaran McCreesh
2007-05-06 19:43 ` Vlastimil Babka
2007-05-06 19:46 ` Ciaran McCreesh [this message]
2007-05-06 16:42 ` Marius Mauch
2007-05-06 17:21 ` Marius Mauch
2007-05-06 17:24 ` expose
2007-05-06 17:31 ` Ciaran McCreesh
2007-05-06 17:38 ` Mike Doty
2007-05-06 17:50 ` expose
2007-05-06 17:58 ` Ciaran McCreesh
2007-05-06 18:08 ` Dan Meltzer
2007-05-06 18:11 ` Ciaran McCreesh
2007-05-06 18:17 ` Dan Meltzer
2007-05-06 18:21 ` Ciaran McCreesh
2007-05-06 18:39 ` Dan Meltzer
2007-05-06 18:42 ` Ciaran McCreesh
2007-05-06 18:53 ` Dan Meltzer
2007-05-06 19:02 ` Ciaran McCreesh
2007-05-06 19:19 ` Dan Meltzer
2007-05-06 19:28 ` Ciaran McCreesh
2007-05-06 19:37 ` Dan Meltzer
2007-05-06 19:44 ` Ciaran McCreesh
2007-05-06 19:24 ` Neil Walker
2007-05-06 18:41 ` expose
2007-05-06 18:47 ` Ciaran McCreesh
2007-05-06 19:26 ` Dan Meltzer
2007-05-06 19:31 ` Ciaran McCreesh
2007-05-06 19:43 ` Dan Meltzer
2007-05-06 19:53 ` Ciaran McCreesh
2007-05-06 20:00 ` Dan Meltzer
2007-05-06 20:06 ` Ciaran McCreesh
2007-05-06 20:13 ` Dan Meltzer
2007-05-06 20:22 ` Ciaran McCreesh
2007-05-06 20:29 ` Dan Meltzer
2007-05-06 21:06 ` Ferris McCormick
2007-05-06 20:33 ` Jakub Moc
2007-05-06 20:38 ` Ciaran McCreesh
2007-05-06 20:50 ` expose
2007-05-06 20:56 ` Ciaran McCreesh
2007-05-06 21:06 ` Jakub Moc
2007-05-06 20:54 ` Dan Meltzer
2007-05-06 18:44 ` Brian Harring
2007-05-06 16:27 ` Hans de Graaff
2007-05-06 16:39 ` Ciaran McCreesh
2007-05-06 17:32 ` expose
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=20070506204636.07564b1b@snowflake \
--to=ciaranm@ciaranm.org \
--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