Re: [gentoo-dev] GLEP 42 "Critical News Reporting" Round Two

[Jason Stubbs]

On Sunday 06 November 2005 02:57, Ciaran McCreesh wrote:
> On Sat, 5 Nov 2005 22:18:14 +0900 Jason Stubbs <jstubbs@g.o>
> | > The following headers are used for filtering. If none of these
> | > headers are specified, the news item is displayed for all users.
> | > Otherwise, the news item is displayed if *at least one* header
> | > matches.
> |
> | It would seem more useful if the headers were sorted into the three
> | classes first. A news item would then only be displayed if a header
> | from the class matches or the class is empty. This would allow for
> | rules such as "net-www/apache is installed and the keyword is either
> | mips or sparc".
>
> Hrm. I'll need to think about that. But it's starting to sound nicer
> than the and/or/none voodoo I'd removed previously.

My sentences aren't making much sense either, even if you got my intention 
anyway. ;)  A news item would then only be displayed if a header from the 
class matches or the class is empty *for each class*.

> | Isn't keyword just a generalization of profile? Why have both?
>
> Simplicity.

Ok. Just confirming.

> | > Thus, all proposed news items must be posted to the ``gentoo-dev``
> | > or ``gentoo-core`` mailing list, and ``Cc:``\ed to
> | > ``pr@g.o`` at least 72 hours before being committed
> | > (exceptions may be made in exceptional circumstances). Any
> | > complaints regarding wording or clarity **must** be addressed
> | > before the news item goes live.
> |
> | Why gentoo-core? It's a news item; it's purpose is to be made public.
>
> Possible security concerns. Hopefully this will never happen.

Ok.

> | Why put this in portage at all? Post sync hooks will likely be
> | available in 2.0.54. If adding hooks were as easy as adding a file to
> | a portage config directory, would adding the package that does the
> | above to the system package set be enough to force this new
> | information dispersal method on users?
>
> Performance. I have a bash script which does the installs that could
> easily be called by a hook, but it has to call portageq quite a bit.
> Otherwise a hook would be fine... Possibly it's fine anyway?

The script could be converted to Python. Or we can have a go at speeding up 
portageq a bit. (Or both ;). It's just that there's only a small part of 
integrated into portage as far as the current GLEP goes, which then partially 
locks people out of working with the news items in alternative ways... Could 
you send over the bash version of the post-sync script?

--
Jason Stubbs
-- 
gentoo-dev@g.o mailing list