From: Leo Famulari <leo@famulari.name>
To: Hartmut Goebel <h.goebel@crazy-compilers.com>
Cc: guix-devel <guix-devel@gnu.org>
Subject: Re: Note for Python packages: packages do not have "inputs" (most of the time)
Date: Tue, 25 Oct 2016 08:49:38 -0400 [thread overview]
Message-ID: <20161025124938.GB887@jasmine> (raw)
In-Reply-To: <580F2A7A.9080406@crazy-compilers.com>
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?
next prev parent reply other threads:[~2016-10-25 12:49 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-23 17:20 Note for Python packages: packages do not have "inputs" (most of the time) Hartmut Goebel
2016-10-23 19:52 ` ng0
2016-10-25 9:48 ` Hartmut Goebel
2016-10-25 12:49 ` Leo Famulari [this message]
2016-10-25 17:59 ` Hartmut Goebel
2016-10-25 18:05 ` Leo Famulari
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20161025124938.GB887@jasmine \
--to=leo@famulari.name \
--cc=guix-devel@gnu.org \
--cc=h.goebel@crazy-compilers.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).