all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Ricardo Wurmus <rekado@elephly.net>
To: ng0 <ng0@infotropique.org>
Cc: guix-devel@gnu.org
Subject: Re: Question about guix system disk-image
Date: Mon, 21 Aug 2017 16:09:20 +0200	[thread overview]
Message-ID: <87efs5vwq7.fsf@elephly.net> (raw)
In-Reply-To: <20170820134425.57ohvu5yy2ux6s2q@abyayala>


ng0 <ng0@infotropique.org> writes:

[…]
> So I think I still don't understand the full PATH perspective/view.
[…]
> My theory is to just add the PATH (to be changed) to PATH.

Do you really mean “PATH” or something else?  “PATH” is only used by the
shell to find the full path to executables when only their names are
given.  This is unrelated to how Guile finds modules.  And that, too, is
unrelated to how “guix system disk-image” works.

> What I'm trying to understand is how I could reduce
> guix system disk-image ~/src/infotropique/infotropique/infotropique/system/install-core.scm
> to just a single infotropique/system/install-core.scm.

“guix system disk-image” takes a (relative or absolute) path to a file.
It then evaluates “(load* the-file-path)”.  If the current working
directory is equal to the directory containing the file then all a user
needs to provide is the basename.  A user can also provide an absolute
path or a relative path (starting from the current work directory).

What matters is only that “load*” gets a file name as an argument.  It
turns the file name into an absolute name and then simply “load”s it.

This bypasses GUILE_LOAD_PATH.

--
Ricardo

GPG: BCA6 89B6 3655 3801 C3C6  2150 197A 5888 235F ACAC
https://elephly.net

      reply	other threads:[~2017-08-21 14:09 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-08-20 13:44 Question about guix system disk-image ng0
2017-08-21 14:09 ` Ricardo Wurmus [this message]

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=87efs5vwq7.fsf@elephly.net \
    --to=rekado@elephly.net \
    --cc=guix-devel@gnu.org \
    --cc=ng0@infotropique.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.
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.