From mboxrd@z Thu Jan  1 00:00:00 1970
From: Leo Famulari <leo@famulari.name>
Subject: Re: Note for Python packages: packages do not have "inputs" (most of
	the time)
Date: Tue, 25 Oct 2016 08:49:38 -0400
Message-ID: <20161025124938.GB887@jasmine>
References: <580CF174.1000201@crazy-compilers.com>
	<87wpgyonb2.fsf@we.make.ritual.n0.is>
	<580F2A7A.9080406@crazy-compilers.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Return-path: <guix-devel-bounces+gcggd-guix-devel=m.gmane.org@gnu.org>
Received: from eggs.gnu.org ([2001:4830:134:3::10]:48760)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <leo@famulari.name>) id 1bz1An-0004H6-51
	for guix-devel@gnu.org; Tue, 25 Oct 2016 08:49:46 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <leo@famulari.name>) id 1bz1Ai-0004VB-61
	for guix-devel@gnu.org; Tue, 25 Oct 2016 08:49:45 -0400
Received: from out1-smtp.messagingengine.com ([66.111.4.25]:44488)
	by eggs.gnu.org with esmtps (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32)
	(Exim 4.71) (envelope-from <leo@famulari.name>) id 1bz1Ah-0004V1-Vs
	for guix-devel@gnu.org; Tue, 25 Oct 2016 08:49:40 -0400
Content-Disposition: inline
In-Reply-To: <580F2A7A.9080406@crazy-compilers.com>
List-Id: "Development of GNU Guix and the GNU System distribution."
	<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" <guix-devel-bounces+gcggd-guix-devel=m.gmane.org@gnu.org>
To: Hartmut Goebel <h.goebel@crazy-compilers.com>
Cc: guix-devel <guix-devel@gnu.org>

On Tue, Oct 25, 2016 at 11:48:42AM +0200, Hartmut Goebel wrote:
> Am 23.10.2016 um 21:52 schrieb ng0:
> > I think this is wrong. My assumption is I work with the old system as
> > long as the new system is not in place. I see no changes which fix this,
> > so why should I do work in advance when this must be fixed afterwards?
> >
> > Will the current system report packages as broken, or are they entirely
> > broken? From my perspective this reads weird. I have not read the new
> > documentation section, but I assumed this is not yet in place?
> 
> The new documentation section is already in place, since it is totally
> independent from the new or the old build system.
> 
> Please note that I'm only asking to stop introducing more broken
> packages (this is using "inputs" for python packages). I'm taking care
> of the existing packages on the wip-python-build-system branch.

Changing the subject: Is that branch stable? Can I start testing core
Python package upgrades on top of it?