all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: ludo@gnu.org (Ludovic Courtès)
To: Arne Babenhauserheide <arne_bab@web.de>
Cc: 15286-done@debbugs.gnu.org
Subject: bug#15286: Add the current directory as GUILE_LOAD_PATH by default
Date: Sat, 14 Sep 2013 14:13:17 +0200	[thread overview]
Message-ID: <87d2obvbxe.fsf@gnu.org> (raw)
In-Reply-To: <1983838.hHcTjoUhmn@fluss> (Arne Babenhauserheide's message of "Sat, 14 Sep 2013 01:05:42 +0200")

Arne Babenhauserheide <arne_bab@web.de> skribis:

> Am Freitag, 6. September 2013, 14:10:27 schrieb Ludovic Courtès:
>> Arne Babenhauserheide <arne_bab@web.de> skribis:
>> 
>> > Currently to install a local package definition, I have to adjust the GUILE_LOAD_PATH by hand:
>> >
>> >       GUILE_LOAD_PATH=. guix package -e '(@ (mercurial) hg)'
>> >
>> > This could be much clearer if the $pwd were in the load path automatically.
>> 
>> As usual, it is a bad idea to include ‘.’ in the search path, because it
>> makes it easy to unwillingly execute untrusted code.
>
> I now learned, that with guile I can use 
>
>     guile -L .
>
> which actually does what I need.
>
> Providing this in guix would be consistent with guile and it would make it really easy to select overlays.

If this is a ‘-L’ option, then I’d say no.  After all, Guix is just
another Guile library, and as such it must not fiddle with the search
path.

Ludo’.

  reply	other threads:[~2013-09-14 12:14 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-09-06  9:29 bug#15286: Add the current directory as GUILE_LOAD_PATH by default Arne Babenhauserheide
2013-09-06 12:10 ` Ludovic Courtès
2013-09-13 23:05   ` Arne Babenhauserheide
2013-09-14 12:13     ` Ludovic Courtès [this message]
2013-09-15 11:24       ` Arne Babenhauserheide
2013-09-15 17:46         ` Mark H Weaver

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=87d2obvbxe.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=15286-done@debbugs.gnu.org \
    --cc=arne_bab@web.de \
    /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.