Gentoo Archives: gentoo-dev

From: Lisa Seelye <lisa@g.o>
To: Kurt Lieber <klieber@g.o>
Cc: Olivier Cr?te <tester@g.o>, gentoo-dev@l.g.o
Subject: Re: [gentoo-dev] RFC: GLEP 19 -- Gentoo Stable Portage Tree
Date: Mon, 02 Feb 2004 22:16:45
Message-Id: 1075753934.12531.32.camel@lisa.thedoh.com
In Reply to: Re: [gentoo-dev] RFC: GLEP 19 -- Gentoo Stable Portage Tree by Kurt Lieber
1 On Mon, 2004-02-02 at 13:31, Kurt Lieber wrote:
2 > > Maybe one year is still too short? I'd propose a much longer period (3
3 > > years), I understand that this is a lot of work for the infrastructure,
4 > > but even at 3 years, its max 12 ebuilds per package...
5 >
6 > I don't object to making it longer, although I think 3 years is sort of
7 > extreme.
8
9 What I think would be beneficial is to have a variable inside the
10 make.conf (and make.globals) to the effect of:
11
12 QUARTERLY_UPDATE_FREQUENCY='12' # update once every 3 years
13 QUARTERLY_UPDATE_FREQUENCY='-1' # never update
14 QUARTERLY_UPDATE_FREQUENCY='0' # update whenever there is a new update
15 (current behavior)
16
17 This would necessitate a file to tell Portage when the last quarterly
18 update was applied.
19
20 You may ask "Why even have these variables?" With security updates it
21 may be beneficial to have `emerge -u world' imply the following logic:
22
23 Basically:
24 if (quarters elapsed since last full update > quarter limit) then
25 apply all updates
26 else if (security updates are available) then
27 apply all security updated updates
28 else
29 do nothing
30 fi
31
32 (I can draw a diagram if necessary...)
33
34
35 --
36 Regards,
37 -Lisa
38 <Quidquid latine dictum sit, altum viditur>

Attachments

File name MIME type
signature.asc application/pgp-signature

Replies

Subject Author
Re: [gentoo-dev] RFC: GLEP 19 -- Gentoo Stable Portage Tree Andrea Barisani <lcars@g.o>