From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from pigeon.gentoo.org ([208.92.234.80] helo=lists.gentoo.org) by finch.gentoo.org with esmtp (Exim 4.60) (envelope-from ) id 1Ri5f5-0003BQ-5q for garchives@archives.gentoo.org; Tue, 03 Jan 2012 14:48:23 +0000 Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id CEBD321C0F6; Tue, 3 Jan 2012 14:48:14 +0000 (UTC) Received: from mail-yw0-f53.google.com (mail-yw0-f53.google.com [209.85.213.53]) by pigeon.gentoo.org (Postfix) with ESMTP id 8240D21C14A for ; Tue, 3 Jan 2012 14:47:12 +0000 (UTC) Received: by yhjj52 with SMTP id j52so10700741yhj.40 for ; Tue, 03 Jan 2012 06:47:12 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=date:from:to:subject:message-id:in-reply-to:references:organization :x-mailer:mime-version:content-type:content-transfer-encoding; bh=hjMiaE2oQQE6ClJpDns2sYNKg1zODpaV1Kz8VfjJg7w=; b=SzWislLjswqc6Xe3qNibo1SZzLCYoLUiV2cIWU4qD/37mFoLwI4hVmIe2ev/sjzTCQ Dk1PEeRhCjNbWFrviclGcf0lnrXqYtLiJcvS+S22wv8Btk373Q2ujQ0JQh8UprlLyLB8 rWsUgH85p0Htfe7T+J3PQXZ67fH/YFxGPSkWg= Received: by 10.236.175.198 with SMTP id z46mr67905736yhl.31.1325602032045; Tue, 03 Jan 2012 06:47:12 -0800 (PST) Received: from rohan.example.com (196-215-2-107.dynamic.isadsl.co.za. [196.215.2.107]) by mx.google.com with ESMTPS id n64sm74696671yhk.4.2012.01.03.06.47.10 (version=SSLv3 cipher=OTHER); Tue, 03 Jan 2012 06:47:11 -0800 (PST) Date: Tue, 3 Jan 2012 16:47:06 +0200 From: Alan McKinnon To: gentoo-user@lists.gentoo.org Subject: Re: [gentoo-user] emerge --update behavior Message-ID: <20120103164706.44c8c328@rohan.example.com> In-Reply-To: <4F030B44.10704@fu-berlin.de> References: <4F00D521.1030702@orlitzky.com> <4F00DA99.8050502@orlitzky.com> <4F00DEC5.5090500@gmail.com> <4F00E741.6050002@orlitzky.com> <4F01CED2.5090806@libertytrek.org> <4F01D6A2.9000002@orlitzky.com> <4F01DC67.7070305@orlitzky.com> <4F01EBBC.5020107@orlitzky.com> <4F01F03B.6090602@orlitzky.com> <4F030B44.10704@fu-berlin.de> Organization: Internet Solutions X-Mailer: Claws Mail 3.7.8 (GTK+ 2.24.4; x86_64-pc-linux-gnu) Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-user@lists.gentoo.org Reply-to: gentoo-user@lists.gentoo.org Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Archives-Salt: e88ff72e-3cc9-4f70-9419-d2336345e18e X-Archives-Hash: bf196ac1d72863e50d71b7a462714e23 On Tue, 03 Jan 2012 15:05:56 +0100 Hinnerk van Bruinehsen wrote: > >> Really, the proposal to 'fix --update' doesn't address really > >> knowing what your system is running and why. Get to the root of > >> that and the --update thing becomes the non-issue that many of us > >> think it is. > >> > > > > This would be a suggestion to travel back in time and document > > something that I have no way of knowing now. > > > You could create your own overlay with "meta"-ebuilds, e. g. > system-maintenance, customer1, customer2. > Inside the ebuilds you define depends on the packages the customer > wants. Doing so you could wipe everything except the "meta"-ebuilds > from world. When a customer quits you can unmerge his or her > "meta"-ebuild and depclean. > If you add everything needed to the respective "meta"-ebuild, you'll > always be on the safe side. Sets do exactly the same thing simply without all the added verbiage of an ebuild. The *only* thing required to bring about the solution you describe is the information in the *DEPEND of the meta-ebuild, and that is all that is in a set. -- Alan McKinnnon alan.mckinnon@gmail.com