Re: [gentoo-dev] Revisiting GLEP 19

[Chris Gianelloni <wolf31o2@gentoo.org>]

[-- Attachment #1: Type: text/plain, Size: 1655 bytes --]

On Wed, 2004-07-21 at 02:50, Daniel Ostrow wrote:
> Most of the sys admins I have worked with belong to 2 schools, #1 is fix
> security issues only and #2 is fix security issues and bugs. Those who
> belong to school #1 generally fix bugs when and only when they directly
> affect the operation of the company and then it is a highly scheduled
> and highly localized event. Those belonging to school #2 usually have
> wider maintenance windows built into their environments so that they can
> achieve a more sweeping update. As such I believe that it is very
> important to delineate weather a package is being updated in the "stable
> tree" for security reasons or to fix a bug, and the changelog for the
> package should have detailed information regarding what the security
> vulnerability/bug is so that sys admins can pick and choose if need be.
> So sys admins also like to be able to do it in one motion so there would
> also have to be a way to "emerge security" and/or "emerge bugfix" the
> same way that we have a emerge world/system now.

My proposal could work with either camp.  I really don't care either
way, as I simply think we need something implemented "soon" to start the
ball rolling and see what happens.  Better to try and fail than to never
try at all and all that jazz....

We would use emerge world to do the same as an emerge security, since
only security fixes would be added...... or..... We would use emerge
world to update everything, and emerge glsa to do only security fixes.

-- 
Chris Gianelloni
Release Engineering QA Manager/Games Developer
Gentoo Linux

Is your power animal a penguin?

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]