[gentoo-dev] Re: Re: GLEP 42 (Was: Getting Important Updates To Users)

[Duncan <1i5t5.duncan@cox.net>]

Jason Stubbs posted <200511051408.09014.jstubbs@gentoo.org>, excerpted
below,  on Sat, 05 Nov 2005 14:08:08 +0900:

> On Saturday 05 November 2005 03:53, Alec Joseph Warner wrote:
>> As far as including news in the tree goes, news is repository bound
>> information.  Each repository may in fact have relevant news, and in
>> preparation for multiple repositories this is how the news should be
>> handled.  It goes with the rest of the repo-specific information.  That
>> is why it should be in the tree.
> 
> I seem to be repeating myself... What's an example of repository-specific 
> non-package-specific news? Why does `emerge --changelog` not suffice for 
> package-specific news?

I'd say it's a matter of degree, or we'd not be having the discussion.

Ideally, there's a changelog entry for /every/ commit.  The specified
purpose of "news" is to convey out-of-the-ordinary changes, where the
Gentoo user (aka Gentoo system sysadmin) needs to be aware of something
unusual, and likely take extraordinary steps to manage the upgrade.
Certainly, "stable on X arch" a bunch of times as a bunch of changelog
entries do not qualify as "out-of-the-ordinary", yet that's the sort of
documentation of changes one expects to fine in a changelog, tho they
would only be "noise" in the proposed "news" system, and shouldn't
generate news messages at all.

Perhaps this is something that needs further clarification in the GLEP?

-- 
Duncan - List replies preferred.   No HTML msgs.
"Every nonfree program has a lord, a master -- 
and if you use the program, he is your master." Richard Stallman in
http://www.linuxdevcenter.com/pub/a/linux/2004/12/22/rms_interview.html


-- 
gentoo-dev@gentoo.org mailing list