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 1R63kF-0005kP-WC for garchives@archives.gentoo.org; Tue, 20 Sep 2011 17:04:32 +0000 Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id A052721C1DF; Tue, 20 Sep 2011 17:04:18 +0000 (UTC) Received: from smtp.gentoo.org (smtp.gentoo.org [140.211.166.183]) by pigeon.gentoo.org (Postfix) with ESMTP id 1584D21C1F5 for ; Tue, 20 Sep 2011 17:03:54 +0000 (UTC) Received: from [192.168.2.3] (dslb-084-058-099-225.pools.arcor-ip.net [84.58.99.225]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) (Authenticated sender: patrick) by smtp.gentoo.org (Postfix) with ESMTPSA id 528F71B4012 for ; Tue, 20 Sep 2011 17:03:53 +0000 (UTC) Message-ID: <4E78C776.5070705@gentoo.org> Date: Tue, 20 Sep 2011 19:03:50 +0200 From: Patrick Lauer User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:6.0) Gecko/20110812 Thunderbird/6.0 Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-dev@lists.gentoo.org Reply-to: gentoo-dev@lists.gentoo.org MIME-Version: 1.0 To: gentoo-dev@lists.gentoo.org Subject: Re: [gentoo-dev] RFC: Making backwards-incompatible tree changes | a solution for GLEP 55's problem References: <20110919221341.GA3211@fury> <4E78AEFC.8080802@gentoo.org> In-Reply-To: <4E78AEFC.8080802@gentoo.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Archives-Salt: X-Archives-Hash: 28f97374c5a15a9ec9dddf3702567e52 On 09/20/11 17:19, Zac Medico wrote: > On 09/19/2011 03:14 PM, Alex Alexander wrote: >> My idea is simple. When incompatible changes have to be introduced to the >> tree, push a new version of portage that includes support for all the new >> features we want to provide. >> >> Then, freeze the tree and clone it into a revbumped rsync module, i.e. >> >> SYNC="rsync://rsync.europe.gentoo.org/gentoo-portage-r1" > It's a waste to provide the old copies via rsync. A similar alternative > that would solve that is to have a file in the tree that maps older > EAPIs to snapshots. That way, after a person syncs and finds that the > tree's EAPI is not supported, their package manager can easily locate > and download a tree snapshot (from any gentoo mirror) which is supported > by the current package manager. Good idea, but won't work retroactively out of the box. So you'd need a helper script to figure out your current state (using portage version and tree snapshot maybe), then prepare the environment to upgrade (and how do you handle the "common" case of python 2.5 only which doesn't allow newest portage anyway?)