From: zimoun <zimon.toutoune@gmail.com>
To: Pierre Neidhardt <mail@ambrevar.xyz>
Cc: Guix Devel <guix-devel@gnu.org>
Subject: Re: Document GUIX_LOAD_PATH?
Date: Wed, 18 Dec 2019 14:17:16 +0100 [thread overview]
Message-ID: <CAJ3okZ3X5DZ3DVDXY5_WHEOzL01=nJGkJeBHZxL-1eLS3x8c8g@mail.gmail.com> (raw)
In-Reply-To: <87pnglj2ka.fsf@ambrevar.xyz>
Hi Pierre,
On Wed, 18 Dec 2019 at 12:28, Pierre Neidhardt <mail@ambrevar.xyz> wrote:
> Today I learned about the existence of GUIX_LOAD_PATH. It does not seem
> to be documented in the manual. Is it anywhere in the doc? Shall we
> document it?
It can be documented in devel pages., maybe Contributing.
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.
Well, for discoverability, it appears to me easier to list an option
with "guix <cmd> --help" than list environment variables.
All the best,
simon
next prev parent reply other threads:[~2019-12-18 13:17 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 [this message]
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 ` Command line option in addition to GUIX_PACKAGE_PATH - Reason? Danny Milosavljevic
2019-12-28 9:56 ` 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='CAJ3okZ3X5DZ3DVDXY5_WHEOzL01=nJGkJeBHZxL-1eLS3x8c8g@mail.gmail.com' \
--to=zimon.toutoune@gmail.com \
--cc=guix-devel@gnu.org \
--cc=mail@ambrevar.xyz \
/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.