From: Cyril Roelandt <tipecaml@gmail.com>
To: guix-devel@gnu.org
Subject: Re: pypi->guix script
Date: Thu, 11 Sep 2014 00:40:49 +0200 [thread overview]
Message-ID: <5410D371.4000903@gmail.com> (raw)
In-Reply-To: <CAJ=RwfYKFc=Y09d8pz+j3Ezsx-DY-buaH1rmsqTVY4iVPMBbGQ@mail.gmail.com>
On 09/09/2014 03:05 PM, Thompson, David wrote:
> On Tue, Sep 9, 2014 at 3:39 AM, Ludovic Court�s <ludo@gnu.org> wrote:
>> On second though, all the importers should have shared infrastructure.
>> There\x19s already the Nix importer, and the \x18guix import\x19 command.
>> Perhaps importers could use \x18guix import\x19 as a shared front-end.
>>
>
> That sounds reasonable. I will try to do that when I get around to
> integrating it with Guix.
>
> Last night, I removed the guile-curl dependency and added another
> backend that generates a package object. I'm debating if I should
> tackle automatically generating the proper inputs before integrating
> it with the rest of Guix.
>
First of all, congrats! This looks really good and will be really useful.
I think you should release early :) It might be quite a pain to list all
inputs: you may have to read (test-)requirements.txt, setup.py (and
maybe actually evaluate some Python code) and deal with less standards
way of listing dependencies. Also, you might need some binaries or C
libraries installed, and it's usually not something that is well
specified in Python packages :/
This looks already good enough to be included; I'd just love to see
something more generic, with an architecture that would make it easy to
package software from other sources, as said in my previous email.
My 2 cents,
Cyril.
next prev parent reply other threads:[~2014-09-10 22:41 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-06 20:10 pypi->guix script David Thompson
2014-09-06 20:36 ` Nikita Karetnikov
2014-09-08 7:06 ` Ludovic Courtès
2014-09-08 13:42 ` Thompson, David
2014-09-08 14:42 ` Ludovic Courtès
2014-09-08 17:19 ` Thompson, David
2014-09-09 7:39 ` Ludovic Courtès
2014-09-09 13:05 ` Thompson, David
2014-09-09 14:11 ` Ludovic Courtès
2014-09-10 22:40 ` Cyril Roelandt [this message]
2014-09-10 22:29 ` Cyril Roelandt
2014-09-11 7:59 ` Ludovic Courtès
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=5410D371.4000903@gmail.com \
--to=tipecaml@gmail.com \
--cc=guix-devel@gnu.org \
/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).