all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: ludo@gnu.org (Ludovic Courtès)
To: Christopher Baines <mail@cbaines.net>
Cc: guix-devel@gnu.org
Subject: Re: Prototype for using Guix with python packages
Date: Sun, 11 Sep 2016 22:34:15 +0200	[thread overview]
Message-ID: <87fup6jhvc.fsf@gnu.org> (raw)
In-Reply-To: <f511d544-3e1f-90de-fe4b-c02730ecf928@cbaines.net> (Christopher Baines's message of "Sun, 11 Sep 2016 15:25:29 +0100")

Hi,

Christopher Baines <mail@cbaines.net> skribis:

> All of this is still very uncertain in my mind, in particular, I see
> Guix as a viable alternative to lots of domain specific package
> managers, which I would really like to avoid when writing software (e.g.
> pip, npm gem) but I'm not certain that being a viable alternative to
> these tools is within the project scope?

Yes and no.  Clearly how NPM and, to a lesser extent, PyPI approach
packaging is very different from how Debian or Guix approach it.

They tend to be very large repos with little or no review, and little
consideration for computing freedom in the case of NPM; they tend to be
mostly automated things that move very fast.

As discussed in another thread, maybe what we can do is provide “core”
packages in Guix proper.  There could be auto-importers for the rest,
but users would have to trust those other repos, which isn’t great.

Then again, importing and maintaining PyPI packages (with the help of
‘guix import’ and ‘guix refresh’) sounds more reasonable than importing
and maintaining NPM stuff.

> The other main uncertainty in my mind is whether the approach I have
> been trying is the best one? I'm getting more confident that this is
> possible, although there are still technical problems (for example,
> adding new versions, without breaking existing versions of other
> packages) that I haven't solved yet.

I think there’s no definite answer; we’ll probably have to explore
different possibilities.

Ludo’.

      reply	other threads:[~2016-09-11 20:34 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-09-06  6:26 Prototype for using Guix with python packages Christopher Baines
2016-09-07 14:01 ` Ludovic Courtès
2016-09-10 13:09   ` Christopher Baines
2016-09-11 13:43     ` Ludovic Courtès
2016-09-11 14:25       ` Christopher Baines
2016-09-11 20:34         ` Ludovic Courtès [this message]

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87fup6jhvc.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=guix-devel@gnu.org \
    --cc=mail@cbaines.net \
    /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 external index

	https://git.savannah.gnu.org/cgit/guix.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.