all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Leo Famulari <leo@famulari.name>
To: David Craven <david@craven.ch>
Cc: guix-devel <guix-devel@gnu.org>
Subject: Re: [PATCH 4/7] gnu: Add spice-gtk.
Date: Sun, 24 Jul 2016 12:21:28 -0400	[thread overview]
Message-ID: <20160724162128.GE32009@jasmine> (raw)
In-Reply-To: <CAL1_im=VOL7Fkcxjzbe=OiR-bQhoaSWbK0e2TtGD5sf0qrbuEg@mail.gmail.com>

On Sun, Jul 24, 2016 at 01:34:13PM +0200, David Craven wrote:
> What are valid reasons to propagate inputs?

Ideally, dependencies can be found by their callers with an absolute
path to /gnu/store/...-foo. But, some software lacks this facility, and
can only find dependencies in the environment, for example on $PATH.

So, when a user installs the calling application into their profile,
propagated-inputs are installed along with it. So, with
~/.guix-profile/bin on the user's PATH, the dependencies are also on
$PATH. This increases the number of potential conflicts in the profile,
so we try to avoid propagating when we can. This is why I asked about
the propagated-inputs in your packages.

Wrappers can be used to avoid propagating in some cases. For example,
the python-build-system wraps all executables with a $PYTHONPATH
containing a list of absolute paths in /gnu/store. You can look at the
store directory of some Python package to see the wrappers.

I'll be happy if someone can correct any inaccuracies in this
explanation :) It's still a bit cloudy for me.

  reply	other threads:[~2016-07-24 16:21 UTC|newest]

Thread overview: 48+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-07-23 13:18 [PATCH 1/7] gnu: Add usbredir David Craven
2016-07-23 13:18 ` [PATCH 2/7] gnu: Add virglrenderer David Craven
2016-07-23 22:04   ` Leo Famulari
2016-07-24 11:07     ` David Craven
2016-07-24 20:29       ` Leo Famulari
2016-07-23 13:18 ` [PATCH 3/7] gnu: Add spice-protocol David Craven
2016-07-23 22:06   ` Leo Famulari
2016-07-23 13:18 ` [PATCH 4/7] gnu: Add spice-gtk David Craven
2016-07-23 22:39   ` Leo Famulari
2016-07-24 11:12     ` David Craven
2016-07-24 11:34       ` David Craven
2016-07-24 16:21         ` Leo Famulari [this message]
2016-07-24 17:59           ` David Craven
2016-07-24 22:14         ` Ludovic Courtès
2016-07-25  7:55           ` David Craven
2016-07-27  9:31             ` David Craven
2016-07-27 22:12               ` Ludovic Courtès
2016-07-27 23:08                 ` Leo Famulari
2016-07-28 16:30                   ` David Craven
2016-07-28 16:59           ` Leo Famulari
2016-07-23 13:18 ` [PATCH 5/7] gnu: Add spice David Craven
2016-07-23 22:40   ` Leo Famulari
2016-07-24 11:19     ` David Craven
2016-07-23 13:18 ` [PATCH 6/7] gnu: Add spice-vdagent David Craven
2016-07-23 22:40   ` Leo Famulari
2016-07-24 11:20     ` David Craven
2016-07-23 13:18 ` [PATCH 7/7] gnu: Add virt-viewer David Craven
2016-07-23 22:40   ` Leo Famulari
2016-07-24 11:31     ` David Craven
2016-07-23 21:46 ` [PATCH 1/7] gnu: Add usbredir Leo Famulari
2016-07-24 17:52   ` David Craven
2016-07-24 17:52     ` [PATCH 2/7] gnu: Add virglrenderer David Craven
2016-07-28 21:09       ` Leo Famulari
2016-07-24 17:52     ` [PATCH 3/7] gnu: Add spice-protocol David Craven
2016-07-28 21:09       ` Leo Famulari
2016-07-24 17:52     ` [PATCH 4/7] gnu: Add spice-gtk David Craven
2016-07-28 21:09       ` Leo Famulari
2016-07-24 17:52     ` [PATCH 5/7] gnu: Add spice David Craven
2016-07-28 21:09       ` Leo Famulari
2016-07-24 17:52     ` [PATCH 6/7] gnu: Add spice-vdagent David Craven
2016-07-28 21:09       ` Leo Famulari
2016-07-24 17:52     ` [PATCH 7/7] gnu: Add virt-viewer David Craven
2016-07-28 21:09       ` Leo Famulari
2016-07-28 21:09     ` [PATCH 1/7] gnu: Add usbredir Leo Famulari
2016-07-29  8:09       ` David Craven
2016-07-29 15:16         ` Leo Famulari
2016-07-29 15:23           ` David Craven
2016-07-30 21:01             ` Andreas Enge

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=20160724162128.GE32009@jasmine \
    --to=leo@famulari.name \
    --cc=david@craven.ch \
    --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 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.