From: Danny Milosavljevic <dannym@scratchpost.org>
To: Pierre Neidhardt <mail@ambrevar.xyz>, zimoun <zimon.toutoune@gmail.com>
Cc: "Guix Devel" <guix-devel@gnu.org>,
"Clément Lassieur" <clement@lassieur.org>
Subject: Command line option in addition to GUIX_PACKAGE_PATH - Reason?
Date: Thu, 26 Dec 2019 21:31:08 +0100 [thread overview]
Message-ID: <20191226213108.753f8ab7@scratchpost.org> (raw)
In-Reply-To: <87lfr8fd9u.fsf@ambrevar.xyz>
[-- Attachment #1: Type: text/plain, Size: 932 bytes --]
Hi Pierre,
Hi zimoun,
On Thu, 19 Dec 2019 18:14:53 +0100
Pierre Neidhardt <mail@ambrevar.xyz> wrote:
> zimoun <zimon.toutoune@gmail.com> writes:
>
> > Do you have in mind commands where the option --load-path is still missing?
> > Maybe "guix graph"?
>
> Yes.
>
> > Maybe "guix edit"?
>
> Yes.
... why? There's the environment variable already--what does it give us
to have yet another way to specify the value?
Shells allow you to do
ENVVAR1=value command1
anyway.
zimoun wrote:
>But IMHO, the normal use should be via the --load-path option and the
>GUIX_LOAD_PATH should be less and less used; stay here for historical
>reason and/or backward compatibility and/or some devel use-case.
Why? *PATH environment variables have a long tradition in UNIX and are not
going to vanish (or mean something else any time) soon. What is the use
case this change is supposed to enable?
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2019-12-26 20:31 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-18 11:28 Document GUIX_LOAD_PATH? Pierre Neidhardt
2019-12-18 13:17 ` zimoun
2019-12-19 10:45 ` Clément Lassieur
2019-12-19 10:59 ` Pierre Neidhardt
2019-12-19 16:57 ` Ludovic Courtès
2019-12-19 17:04 ` Pierre Neidhardt
2019-12-19 17:09 ` zimoun
2019-12-19 17:14 ` Pierre Neidhardt
2019-12-26 20:31 ` Danny Milosavljevic [this message]
2019-12-28 9:56 ` Command line option in addition to GUIX_PACKAGE_PATH - Reason? Pierre Neidhardt
2019-12-30 18:29 ` zimoun
2020-01-16 14:30 ` Pierre Neidhardt
2020-01-16 16:12 ` zimoun
2020-01-17 15:56 ` Pierre Neidhardt
2020-01-17 16:19 ` [bug#38678] " zimoun
2020-01-17 16:56 ` Pierre Neidhardt
2020-01-17 18:14 ` zimoun
2020-01-17 18:38 ` Pierre Neidhardt
2020-01-18 12:01 ` Pierre Neidhardt
2020-01-18 12:09 ` Pierre Neidhardt
2020-01-20 16:21 ` zimoun
2020-01-20 18:12 ` Pierre Neidhardt
2020-01-20 18:35 ` zimoun
2019-12-19 21:13 ` Document GUIX_LOAD_PATH? zimoun
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=20191226213108.753f8ab7@scratchpost.org \
--to=dannym@scratchpost.org \
--cc=clement@lassieur.org \
--cc=guix-devel@gnu.org \
--cc=mail@ambrevar.xyz \
--cc=zimon.toutoune@gmail.com \
/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.