From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from lists.gentoo.org ([140.105.134.102] helo=robin.gentoo.org) by nuthatch.gentoo.org with esmtp (Exim 4.43) id 1DqudU-0002Qj-1x for garchives@archives.gentoo.org; Fri, 08 Jul 2005 15:19:28 +0000 Received: from robin.gentoo.org (localhost [127.0.0.1]) by robin.gentoo.org (8.13.4/8.13.4) with SMTP id j68FIDWB005346; Fri, 8 Jul 2005 15:18:13 GMT Received: from easycgi.com (mail.easycgi.com [66.245.177.160]) by robin.gentoo.org (8.13.4/8.13.4) with ESMTP id j68FIBJr016296 for ; Fri, 8 Jul 2005 15:18:12 GMT Received: from [68.89.14.73] (HELO smurf.sixthings.net) by easycgi.com (CommuniGate Pro SMTP 4.2.3) with ESMTP id 2297697 for gentoo-portage-dev@lists.gentoo.org; Fri, 08 Jul 2005 11:18:21 -0400 From: Robert Larson Organization: Six Things Inc. To: gentoo-portage-dev@lists.gentoo.org Subject: Re: [gentoo-portage-dev] Proposal: pre-emerge advisories Date: Fri, 8 Jul 2005 10:18:33 -0500 User-Agent: KMail/1.7.2 References: <1120808406.15666.32.camel@localhost.localdomain> In-Reply-To: <1120808406.15666.32.camel@localhost.localdomain> Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-portage-dev@gentoo.org Reply-to: gentoo-portage-dev@lists.gentoo.org MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200507081018.33085.robert@sixthings.com> X-Archives-Salt: 40efbf86-d8c6-46f1-ba01-610fecff2e20 X-Archives-Hash: bde8794f35485ed37a23fc0f80441e0c > Regardless of implementation, the main goals are: > 1. Adding or modifying advisories is relatively easy. Doesn't require > programming skills. > 2. Adding an advisory in no way risks an ebuild file. An ebuild is > executable code and no one has time to chase down syntax errors. > Advisories are separate. > 3. You don't need to be the package maintainer to do it (though at this > point I'm not sure who would -- maybe a collaboration of forum > moderators and package maintainers?). Though it's been many moons, and major versions since my last set of major issues with Gentoo upgrades, I would have to agree. I have a set of servers that I am constantly upgrading to minimize the risk of a bunch of breaks in order to only receive a few. For instance, I have overlooked the currently implemented messages in the past due to unattended upgrades. Some of the worse breaks I've had have, on occasion, completely crippled a system. I have started building binary packages as well in an attempt to revert if stuff fails, but sometimes even that doesn't help. Something to this order would be very beneficial. I have currently established a system where I periodically check my scrollback buffer until I find some emerge notes at the end of a package installation. From here I copy and paste the notes into files that I so elloquently name "emerge..log". This is the easiest way I know to do it. I have looked at the ebuilds before for package information, but this is only helpful if I know that I've missed something, as I don't have time to go over every package that gets installed or upgraded. Usually my process of upgrades consists of simply determining if I need the package or not. I have been trying to find something to this resolve, cause frankly, my system sucks and I know it's probably not the best. For me it's the quickest, and I was not able to think of anything else. This is why I believe you're on the right track. I hope this input helps. Thank you, Robert Larson -- gentoo-portage-dev@gentoo.org mailing list