From: Pierre Neidhardt <ambrevar@gmail.com>
To: Chris Marusich <cmmarusich@gmail.com>
Cc: help-guix <help-guix@gnu.org>
Subject: Re: Package request inxi
Date: Thu, 12 Apr 2018 14:39:41 +0530 [thread overview]
Message-ID: <874lkgpz8q.fsf@gmail.com> (raw)
In-Reply-To: <87muy8dcvl.fsf@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1030 bytes --]
See https://github.com/smxi/inxi: it's a Perl script that calls various
programs (if it finds them) _at runtime_.
Basically inxi makes a number of `system PROGRAM` calls, where PROGRAM
is found in the PATH environment variable.
Because most of those dependencies are optional, it could be nice not
depend on them. Which means no input at build-time. But then we cannot
substitute the relative paths by the static full path to the store.
Another approach would be to _not_ have optional dependencies are go
more Nix-y as you suggest with including all the required programs as
input and storing their full path inside the inxi script.
This is hard though, because it implies parsing a huge Perl script...
We could also go the dead-simple way: leave PATH and paths to their
current values: the only downside I see is that inxi could pententially
call programs of the same name installed in user-specific folders
(e.g. ~/.local/bin).
--
Pierre Neidhardt
To save a single life is better than to build a seven story pagoda.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 487 bytes --]
next prev parent reply other threads:[~2018-04-12 9:09 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-28 14:02 Package requests: fortune, gifsicle, inxi, uncrustify, unrar, vsftp, xss-lock Pierre Neidhardt
2018-03-28 15:27 ` Package request inxi Oleg Pykhalov
2018-03-28 17:26 ` Pierre Neidhardt
2018-04-11 16:17 ` Pierre Neidhardt
2018-04-11 17:23 ` Oleg Pykhalov
2018-04-11 17:29 ` Pierre Neidhardt
2018-04-11 17:34 ` Pierre Neidhardt
2018-04-11 18:14 ` Oleg Pykhalov
2018-04-12 7:15 ` Pierre Neidhardt
2018-04-12 7:24 ` Pierre Neidhardt
2018-04-12 8:53 ` Chris Marusich
2018-04-12 9:09 ` Pierre Neidhardt [this message]
2018-04-11 17:42 ` Oleg Pykhalov
2018-04-12 5:29 ` Pierre Neidhardt
2018-04-12 8:25 ` Chris Marusich
2018-04-12 8:39 ` Pierre Neidhardt
2018-04-12 17:07 ` inxi and inxi-full Oleg Pykhalov
2018-04-12 17:19 ` Pierre Neidhardt
2018-04-13 3:41 ` Chris Marusich
2018-04-13 4:00 ` Pierre Neidhardt
2018-04-13 5:11 ` Chris Marusich
2018-04-13 5:52 ` Pierre Neidhardt
2018-04-13 6:13 ` Chris Marusich
2018-04-13 6:24 ` Pierre Neidhardt
2018-04-14 6:22 ` Pierre Neidhardt
2018-04-16 6:59 ` Chris Marusich
2018-04-16 7:16 ` Pierre Neidhardt
2018-04-16 10:26 ` gnu: Add inxi (old Shell script version) Oleg Pykhalov
2018-04-16 10:31 ` Pierre Neidhardt
2018-03-31 5:15 ` Package requests: fortune, gifsicle, inxi, uncrustify, unrar, vsftp, xss-lock Pierre Neidhardt
2018-04-01 12:15 ` Pierre Neidhardt
2018-04-12 13:04 ` Ricardo Wurmus
2018-04-12 17:00 ` Leo Famulari
2018-04-12 17:13 ` Clément Lassieur
2018-04-12 17:17 ` Pierre Neidhardt
2018-04-12 17:23 ` Marius Bakke
2018-04-12 17:34 ` Pierre Neidhardt
2018-04-12 17:41 ` Clément Lassieur
2018-04-12 17:53 ` Pierre Neidhardt
2018-04-21 19:18 ` File sharing with GNU Guix (was: Re: Package requests: fortune, gifsicle, inxi, uncrustify, unrar, vsftp, xss-lock) Chris Marusich
2018-04-22 5:58 ` Pierre Neidhardt
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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=874lkgpz8q.fsf@gmail.com \
--to=ambrevar@gmail.com \
--cc=cmmarusich@gmail.com \
--cc=help-guix@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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).