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 1Rhq9Z-0002x1-Hy for garchives@archives.gentoo.org; Mon, 02 Jan 2012 22:14:49 +0000 Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 9B78221C067; Mon, 2 Jan 2012 22:14:34 +0000 (UTC) Received: from mail2.viabit.com (mail2.viabit.com [65.246.80.16]) by pigeon.gentoo.org (Postfix) with ESMTP id AB8FB21C03B for ; Mon, 2 Jan 2012 22:13:04 +0000 (UTC) Received: from [172.17.29.6] (unknown [65.213.236.242]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail2.viabit.com (Postfix) with ESMTPSA id 14E7C3837D for ; Mon, 2 Jan 2012 17:13:03 -0500 (EST) DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=orlitzky.com; s=mail2; t=1325542384; bh=6fsrevuKmUel2sDO49vqyeci1fc+FxaCEwrUT4kkG/w=; h=Message-ID:Date:From:MIME-Version:To:Subject:References: In-Reply-To:Content-Type:Content-Transfer-Encoding; b=Lsc68Jf6pizaOKmqeXVOAqnsawEQR98eJeb6rPqMXv5dJp0iaJ0gK2Lz9mrqdCGYm c29nf5FOskroONDF2NcREkS7LCobKjnKtpyY+a+vItLfjVx8PUOIwvk9Qh3tv0Oi0a +I3nhAME4GbjVBUpH5fYPpZmY57m9ufDntYBHJlI= Message-ID: <4F022BEE.2050103@orlitzky.com> Date: Mon, 02 Jan 2012 17:13:02 -0500 From: Michael Orlitzky User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:8.0) Gecko/20111202 Thunderbird/8.0 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 To: gentoo-user@lists.gentoo.org Subject: Re: [gentoo-user] emerge --update behavior 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> <20120102231103.58da25d5@rohan.example.com> <4F021F1F.3090807@orlitzky.com> <4F022647.4050903@orlitzky.com> In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-Archives-Salt: 04708b59-1fe5-4401-8940-c8e22bc2c7e0 X-Archives-Hash: 5f07061e52f149e7fa90fbd7c9b802bb On 01/02/2012 04:58 PM, Michael Mol wrote: > > Ah. I must have gotten confused at "So which ones can I remove? > Solutions involving time travel and/or losing customers will be > disqualified." > Sorry, this thread has gotten a little out of hand =) I think my point was: most solutions available to me now involve potential breakage. Others require me to be more careful 6 years ago. Neither of those is desirable. The current --update behavior makes this situation easy to get into. If there are no downsides to the old behavior (the point of this thread), then I think the old behavior is preferable.