From mboxrd@z Thu Jan  1 00:00:00 1970
From: Andreas Enge <andreas@enge.fr>
Subject: Re: [PATCH] gnu: Add Python 3.
Date: Sun, 1 Sep 2013 21:50:46 +0200
Message-ID: <20130901195046.GA4912@debian>
References: <1377644626-17292-1-git-send-email-tipecaml@gmail.com>
	<8761ukoct3.fsf@gnu.org> <20130901144110.GA23502@debian>
	<874na4ib4k.fsf@gnu.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 8bit
Return-path: <guix-devel-bounces+gcggd-guix-devel=m.gmane.org@gnu.org>
Received: from eggs.gnu.org ([2001:4830:134:3::10]:33194)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <andreas@enge.fr>) id 1VGDfm-0004Tc-S7
	for guix-devel@gnu.org; Sun, 01 Sep 2013 15:51:06 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <andreas@enge.fr>) id 1VGDff-0003Vq-Ic
	for guix-devel@gnu.org; Sun, 01 Sep 2013 15:50:58 -0400
Received: from moutng.kundenserver.de ([212.227.17.9]:58999)
	by eggs.gnu.org with esmtp (Exim 4.71)
	(envelope-from <andreas@enge.fr>) id 1VGDff-0003Vl-8q
	for guix-devel@gnu.org; Sun, 01 Sep 2013 15:50:51 -0400
Content-Disposition: inline
In-Reply-To: <874na4ib4k.fsf@gnu.org>
List-Id: <guix-devel.gnu.org>
List-Unsubscribe: <https://lists.gnu.org/mailman/options/guix-devel>,
	<mailto:guix-devel-request@gnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/archive/html/guix-devel>
List-Post: <mailto:guix-devel@gnu.org>
List-Help: <mailto:guix-devel-request@gnu.org?subject=help>
List-Subscribe: <https://lists.gnu.org/mailman/listinfo/guix-devel>,
	<mailto:guix-devel-request@gnu.org?subject=subscribe>
Errors-To: guix-devel-bounces+gcggd-guix-devel=m.gmane.org@gnu.org
Sender: guix-devel-bounces+gcggd-guix-devel=m.gmane.org@gnu.org
To: guix-devel@gnu.org

On Sun, Sep 01, 2013 at 09:40:27PM +0200, Ludovic Courtès wrote:
> Speaking of which: in the future, we should use topic branches for such
> things, to avoid disrupting the main branch.  For instance, I’ve locally
> switched back to Python 2 as the default since I was otherwise unable to
> use the QEMU-related things.
> 
> Actually it’s not too late: we could create a new branch off ‘master’,
> and just switch back to Python 2 as the default on ‘master’.  Hydra can
> be told to build the new branch in addition to ‘master’.

Actually, 77c7f8f41b558bab13690c843068af8ba996e5bf switches back (while
keeping the definition of Python 3 in the variable python-3; but all
packages using python as input will get Python 2).

We could create branches; very often (like here, with changes to the python
build system pending), we might as well use core-updates directly.

Andreas