all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
* Which inputs to define for 'meta' utilities?
@ 2018-02-03 11:37 Hartmut Goebel
  2018-02-05 13:21 ` Ludovic Courtès
  0 siblings, 1 reply; 2+ messages in thread
From: Hartmut Goebel @ 2018-02-03 11:37 UTC (permalink / raw)
  To: guix-devel

[-- Attachment #1: Type: text/plain, Size: 640 bytes --]

Hi,

I'm about to package dtrx <https://brettcsmith.org/2007/dtrx/>, a script
to intelligently extract multiple archive types. The script determines
the archive format and calls the respective extraction tool, which it
searches on the $PATH.

1) Should I add all required tools as inputs?

2) Should I use propagated inputs then? The executable are searched on
$PATH.


FYJ: Debian includes all the required inputs, see
<https://packages.debian.org/stretch/dtrx>.

-- 
Regards
Hartmut Goebel

| Hartmut Goebel          | h.goebel@crazy-compilers.com               |
| www.crazy-compilers.com | compilers which you thought are impossible |


[-- Attachment #2: 0xBF773B65.asc --]
[-- Type: application/pgp-keys, Size: 14855 bytes --]

^ permalink raw reply	[flat|nested] 2+ messages in thread

* Re: Which inputs to define for 'meta' utilities?
  2018-02-03 11:37 Which inputs to define for 'meta' utilities? Hartmut Goebel
@ 2018-02-05 13:21 ` Ludovic Courtès
  0 siblings, 0 replies; 2+ messages in thread
From: Ludovic Courtès @ 2018-02-05 13:21 UTC (permalink / raw)
  To: Hartmut Goebel; +Cc: guix-devel

Hi,

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

> I'm about to package dtrx <https://brettcsmith.org/2007/dtrx/>, a script
> to intelligently extract multiple archive types. The script determines
> the archive format and calls the respective extraction tool, which it
> searches on the $PATH.
>
> 1) Should I add all required tools as inputs?
>
> 2) Should I use propagated inputs then? The executable are searched on
> $PATH.

Option #2 is a bad idea (propagated inputs should be used only as a last
resort.)

Adding the tools as inputs is only useful if there are tests that
actually run dtrx; otherwise it’s useless.

Then you have two options:

  1. Let dtrx search for tools in $PATH.  The downside is that it won’t
     work out-of-the-box, as in “guix environment -C --ad-hoc dtrx”.

  2. Hard-code the absolute file names for the tools in question in
     dtrx.  That way ‘guix pack dtrx’ will be self-contained, etc.

I’d prefer #2.

Ludo’.

^ permalink raw reply	[flat|nested] 2+ messages in thread

end of thread, other threads:[~2018-02-05 13:21 UTC | newest]

Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2018-02-03 11:37 Which inputs to define for 'meta' utilities? Hartmut Goebel
2018-02-05 13:21 ` Ludovic Courtès

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.