all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: ludo@gnu.org (Ludovic Courtès)
To: Andreas Enge <andreas@enge.fr>
Cc: guix-devel@gnu.org, Federico Beffa <beffa@ieee.org>
Subject: Re: wrap-program
Date: Thu, 02 Oct 2014 10:41:39 +0200	[thread overview]
Message-ID: <87lhoy6eyk.fsf@gnu.org> (raw)
In-Reply-To: <20141002070921.GA25816@debian> (Andreas Enge's message of "Thu, 2 Oct 2014 09:09:21 +0200")

Andreas Enge <andreas@enge.fr> skribis:

> I am only now catching up with the discussion. So far, I do not understand
> why we need a wrapper. Would it not be enough to add the environment variables
> $XDG_DATA_DIRS etc. to the search paths of the programs, in the same way as
> perl or python modules incite the user to define the corresponding environment
> variables pointing to a subdirectory of .guix-profile?

There are several things to consider.  First, it’s better if things work
out of the box.

Second, sometimes, we may want to trade dynamicity for reproducibility
(and “referential transparency.”)  In the case of GTK+ plug-ins, if we
force GTK_EXE_PREFIX in a wrapper, then we make sure the application is
using the “right” plug-ins, at the cost of making the system more
static.  For schemas, having XDG_DATA_DIRS defined in a wrapper would
just make sure that the application actually works (otherwise it could
end up using the wrong schemas, I suppose.)

My 2¢,
Ludo’.

  reply	other threads:[~2014-10-02  8:41 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-09-13 13:13 emacs package Federico Beffa
2014-09-15  7:55 ` Ludovic Courtès
2014-09-16  7:38   ` Federico Beffa
2014-09-16 20:04     ` Federico Beffa
2014-09-17  9:11       ` Ludovic Courtès
2014-09-17 16:57         ` Federico Beffa
2014-09-18 12:01           ` Ludovic Courtès
2014-09-18 18:37             ` Federico Beffa
2014-09-19  7:54               ` Ludovic Courtès
2014-09-19  8:07                 ` Andreas Enge
2014-09-19 17:13                 ` Federico Beffa
2014-09-19 17:32                   ` Andreas Enge
2014-09-20 13:20                   ` Ludovic Courtès
2014-09-20 19:57                     ` Federico Beffa
2014-09-20 20:28                       ` Ludovic Courtès
2014-09-20 22:02                         ` Federico Beffa
2014-09-22  7:38                           ` GSettings schemas Ludovic Courtès
2014-09-23 18:39                             ` Mark H Weaver
2014-09-24  7:11                               ` wrap-program Ludovic Courtès
2014-09-26 20:09                                 ` wrap-program Federico Beffa
2014-09-26 22:17                                   ` wrap-program Federico Beffa
2014-09-27  9:20                                   ` wrap-program Ludovic Courtès
2014-09-27 14:53                                     ` wrap-program Federico Beffa
2014-10-02  7:09                                       ` wrap-program Andreas Enge
2014-10-02  8:41                                         ` Ludovic Courtès [this message]
2014-09-21 13:28                     ` emacs package Ludovic Courtès
2014-09-21 19:40                       ` Federico Beffa

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=87lhoy6eyk.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=andreas@enge.fr \
    --cc=beffa@ieee.org \
    --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.