[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Note for Python packages: packages do not have "inputs" (most of the
|
From: |
Leo Famulari |
|
Subject: |
Re: Note for Python packages: packages do not have "inputs" (most of the time) |
|
Date: |
Tue, 25 Oct 2016 08:49:38 -0400 |
|
User-agent: |
Mutt/1.7.0 (2016-08-17) |
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?