Gentoo Archives: gentoo-dev

From: Dan Meltzer <parallelgrapefruit@×××××.com>
To: gentoo-dev@l.g.o
Subject: Re: [gentoo-dev] GLEP 42 "Critical News Reporting" Round Two
Date: Fri, 11 Nov 2005 04:11:42
Message-Id: 46059ce10511102009u2631ef63wa4f26103a8875c84@mail.gmail.com
In Reply to: Re: [gentoo-dev] GLEP 42 "Critical News Reporting" Round Two by Luca Barbato
1 Forever.
2
3 Gentoo releases mean absolutely nothing, they do absolutely nothing.
4
5 The news should stay until the upgrade occurs
6
7 On 11/10/05, Luca Barbato <lu_zero@g.o> wrote:
8 > Ciaran McCreesh wrote:
9 > > On Thu, 10 Nov 2005 16:07:37 -0800 Mike Owen <kyphros@×××××.com> wrote:
10 > > | What about something like "/etc/portage/news.read", which contains a
11 > > | single news file per line. Perhaps have support for something like
12 > > | "<=2006-01-01" in order to be able to manually mark date ranges as
13 > > | read.
14 > >
15 > > Eh, yet another file. No real need for it really, it just adds
16 > > complexity.
17 > >
18 > > Besides, /etc isn't for program-generated data.
19 > >
20 >
21 > Modify anything within PORTDIR is wrong.
22 >
23 > I'd put a /var/db/news and a /etc/portage/news to handle that.
24 >
25 > Which should be a reasonable timeframe for the news to stay?
26 >
27 > Till the next gentoo release?
28 >
29 > lu
30 >
31 > --
32 >
33 > Luca Barbato
34 >
35 > Gentoo/linux Developer Gentoo/PPC Operational Leader
36 > http://dev.gentoo.org/~lu_zero
37 >
38 > --
39 > gentoo-dev@g.o mailing list
40 >
41 >
42
43 --
44 gentoo-dev@g.o mailing list

Replies

Subject Author
Re: [gentoo-dev] GLEP 42 "Critical News Reporting" Round Two Luca Barbato <lu_zero@g.o>
[gentoo-dev] Re: GLEP 42 "Critical News Reporting" Round Two R Hill <dirtyepic.sk@×××××.com>