On Mon, 2004-02-02 at 13:31, Kurt Lieber wrote: > > Maybe one year is still too short? I'd propose a much longer period (3 > > years), I understand that this is a lot of work for the infrastructure, > > but even at 3 years, its max 12 ebuilds per package... > > I don't object to making it longer, although I think 3 years is sort of > extreme.
What I think would be beneficial is to have a variable inside the make.conf (and make.globals) to the effect of: QUARTERLY_UPDATE_FREQUENCY='12' # update once every 3 years QUARTERLY_UPDATE_FREQUENCY='-1' # never update QUARTERLY_UPDATE_FREQUENCY='0' # update whenever there is a new update (current behavior) This would necessitate a file to tell Portage when the last quarterly update was applied. You may ask "Why even have these variables?" With security updates it may be beneficial to have `emerge -u world' imply the following logic: Basically: if (quarters elapsed since last full update > quarter limit) then apply all updates else if (security updates are available) then apply all security updated updates else do nothing fi (I can draw a diagram if necessary...) -- Regards, -Lisa <Quidquid latine dictum sit, altum viditur>
signature.asc
Description: This is a digitally signed message part
