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 1R627z-0004Y8-Jj for garchives@archives.gentoo.org; Tue, 20 Sep 2011 15:20:55 +0000 Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id A9F8C21C2F9; Tue, 20 Sep 2011 15:20:31 +0000 (UTC) Received: from smtp.gentoo.org (smtp.gentoo.org [140.211.166.183]) by pigeon.gentoo.org (Postfix) with ESMTP id 686AF21C0DF for ; Tue, 20 Sep 2011 15:19:27 +0000 (UTC) Received: from [192.168.26.4] (ip98-164-193-252.oc.oc.cox.net [98.164.193.252]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) (Authenticated sender: zmedico) by smtp.gentoo.org (Postfix) with ESMTPSA id 9F95A1B401A for ; Tue, 20 Sep 2011 15:19:25 +0000 (UTC) Message-ID: <4E78AEFC.8080802@gentoo.org> Date: Tue, 20 Sep 2011 08:19:24 -0700 From: Zac Medico User-Agent: Mozilla/5.0 (X11; Linux i686 on x86_64; rv:6.0) Gecko/20110827 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> In-Reply-To: <20110919221341.GA3211@fury> X-Enigmail-Version: 1.3 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Archives-Salt: X-Archives-Hash: be1679d93458c5bd613c2679559ba70e 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. -- Thanks, Zac