From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 2938 invoked from network); 21 Jul 2004 20:00:09 +0000 Received: from smtp.gentoo.org (156.56.111.197) by lists.gentoo.org with AES256-SHA encrypted SMTP; 21 Jul 2004 20:00:09 +0000 Received: from lists.gentoo.org ([156.56.111.196] helo=parrot.gentoo.org) by smtp.gentoo.org with esmtp (Exim 4.34) id 1BnNFz-0006gz-VK for arch-gentoo-dev@lists.gentoo.org; Wed, 21 Jul 2004 20:00:04 +0000 Received: (qmail 22030 invoked by uid 89); 21 Jul 2004 20:00:03 +0000 Mailing-List: contact gentoo-dev-help@gentoo.org; run by ezmlm Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-dev@gentoo.org Received: (qmail 12281 invoked from network); 21 Jul 2004 20:00:03 +0000 From: Chris Gianelloni Reply-To: wolf31o2@gentoo.org To: gentoo-dev@lists.gentoo.org In-Reply-To: <40FE121B.3040206@gentoo.org> References: <20040720131405.GW18023@mail.lieber.org> <40FDCD20.6080302@scms.waikato.ac.nz> <40FE121B.3040206@gentoo.org> Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="=-o66/JivRKG6lDUTzyl+0" Organization: Gentoo Linux Message-Id: <1090441548.19552.129.camel@localhost> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.4.6 Date: Wed, 21 Jul 2004 16:25:48 -0400 Subject: Re: [gentoo-dev] Revisiting GLEP 19 X-Archives-Salt: 2359cef8-1ba8-4a03-a480-1e250c627af3 X-Archives-Hash: dfa7f2611fc156291b55d0f32325010f --=-o66/JivRKG6lDUTzyl+0 Content-Type: text/plain Content-Transfer-Encoding: quoted-printable 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. --=20 Chris Gianelloni Release Engineering QA Manager/Games Developer Gentoo Linux Is your power animal a penguin? --=-o66/JivRKG6lDUTzyl+0 Content-Type: application/pgp-signature; name=signature.asc Content-Description: This is a digitally signed message part -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.4 (GNU/Linux) iD8DBQBA/tFMkT4lNIS36YERAv5FAJ4yiqHgOGMYnva9W7acn+BPIQr7iQCgvRwj vZbL3iX2IJs2CUwdZVfNOqk= =9Xp9 -----END PGP SIGNATURE----- --=-o66/JivRKG6lDUTzyl+0--