From: John Darrington <john@darrington.wattle.id.au>
To: Chris Marusich <cmmarusich@gmail.com>
Cc: guix-devel@gnu.org
Subject: Re: [PATCH] gnu: Add asunder.
Date: Sun, 25 Dec 2016 08:48:35 +0100 [thread overview]
Message-ID: <20161225074835.GA9450@jocasta.intra> (raw)
In-Reply-To: <87mvfkn4se.fsf@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2347 bytes --]
On Sat, Dec 24, 2016 at 06:03:45PM -0800, Chris Marusich wrote:
Why is the wrapper not good here? What would be a better solution?
Here's why I think the wrapper produced by 'wrap-program' is a good
solution in this case:
* The wrapper script allows us to package the software without modifying
its source. As previously explained, Asunder is currently written under
the assumption that the tools it requires will be made available via the
PATH environment variable.
* The wrapper script guarantees "complete deployment" of Asunder (i.e.,
no missing dependencies). This is because the wrapper script contains
references to the components in the store that provide the command-line
tools that Asunder requires.
* The wrapper script requires less work than patching Asunder.
* The wrapper script is more robust than any patch we might attempt to
apply to Asunder's source code.
This is a good argument for using a wrapper script in this case. And I
believe these points apply to any component, like Asunder, which is
written under the assumption that tools will be made available via
PATH. I also am willing to believe there are cases where the wrapper
script is undesirable, but I don't think this is one of them.
If there's a better way to package Asunder, I'm happy to do it.
However, I haven't heard of any concrete alternatives, or any concrete
explanations of why a wrapper is undesirable. Until then, I think using
a wrapper like this to package components like Asunder is the best way.
I think all your arguments are valid, and I am not disagreeing with you.
I am merely presenting a counter argument for you to consider.
My problem with wrappers is that 1) it makes it difficult for a users
to override environment variables, if they want to for some reason. 2)
programs which the user expects to be a binary are in fact an shell
script, adding a layer of confusion.
Just my $0.02.
J'
--
Avoid eavesdropping. Send strong encrypted email.
PGP Public key ID: 1024D/2DE827B3
fingerprint = 8797 A26D 0854 2EAB 0285 A290 8A67 719C 2DE8 27B3
See http://sks-keyservers.net or any PGP keyserver for public key.
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 181 bytes --]
next prev parent reply other threads:[~2016-12-25 7:49 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-17 9:20 Add Asunder Chris Marusich
2016-12-17 9:20 ` [PATCH] gnu: Add asunder Chris Marusich
2016-12-17 9:46 ` John Darrington
2016-12-17 16:14 ` Hartmut Goebel
2016-12-17 18:56 ` Leo Famulari
2016-12-18 9:04 ` Chris Marusich
2016-12-23 8:16 ` Chris Marusich
2016-12-23 16:36 ` Leo Famulari
2016-12-24 2:11 ` Chris Marusich
2016-12-24 7:07 ` John Darrington
2016-12-25 2:03 ` Chris Marusich
2016-12-25 7:48 ` John Darrington [this message]
2016-12-25 20:03 ` Leo Famulari
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=20161225074835.GA9450@jocasta.intra \
--to=john@darrington.wattle.id.au \
--cc=cmmarusich@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 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.