all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: ludo@gnu.org (Ludovic Courtès)
To: Hartmut Goebel <h.goebel@crazy-compilers.com>
Cc: guix-devel <guix-devel@gnu.org>
Subject: Re: Language library packages should require language package
Date: Mon, 25 Apr 2016 00:07:23 +0200	[thread overview]
Message-ID: <87r3du8xus.fsf@gnu.org> (raw)
In-Reply-To: <571CD10F.1010906@crazy-compilers.com> (Hartmut Goebel's message of "Sun, 24 Apr 2016 15:58:39 +0200")

Hartmut Goebel <h.goebel@crazy-compilers.com> skribis:

> But you are missing my main point: While `guix environment --ad-hoc
> python-requests` installs some depended python packages, it does not
> install `python`. This is asymmetric and quite different than users are
> used from rpm and deb based systems.

Indeed.  I understand this is surprising.  It stems from the fact that
Guix doesn’t know about the relation between ‘python-requests’ and
‘python’.

Even if it did, it’s not clear to me that automatically installing both
would be a good idea.  There are cases where one may want to choose a
particular variant of the ‘python’ package rather than have an
arbitrarily chosen default.

Does it make sense?

> To take this one step further: Assume in GuixSD 1.3 some user is told
> "install python-bla-blub vai the Guix Package Manager GUI", then she
> ends up with an incomplete environment. She would have to figure out
> what other dependencies (esp. the language interpreter) are required.

Most likely one would provide a file that can be passed to ‘guix
environment -l’ instead of writing down the instructions.  :-)

Thanks,
Ludo’.

  reply	other threads:[~2016-04-24 22:07 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-04-24 12:24 Language library packages should require language package Hartmut Goebel
2016-04-24 13:09 ` Thompson, David
2016-04-24 13:58   ` Hartmut Goebel
2016-04-24 22:07     ` Ludovic Courtès [this message]
2016-04-24 13:17 ` Thompson, David

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=87r3du8xus.fsf@gnu.org \
    --to=ludo@gnu.org \
    --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 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.