all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: ng0 <ng0@infotropique.org>
To: guix-devel@gnu.org
Subject: Question about guix system disk-image
Date: Sun, 20 Aug 2017 13:44:25 +0000	[thread overview]
Message-ID: <20170820134425.57ohvu5yy2ux6s2q@abyayala> (raw)

[-- Attachment #1: Type: text/plain, Size: 1249 bytes --]

To quote myself in full (with some corrections):

I have a rather easy question about the guix system disk-image command.
I have read most of the code around it. We seem to not auto-compile the
gnu/system/install.scm module, we just use it as an argument. So far I
just assumed this only works when you are in the root of the git checkout
of the guix source.
So I think I still don't understand the full PATH perspective/view.
Will it work when I move elsewhere? Do I have to have the git checkout
or could we move it whereever and it'd still be functional?

Any further modules I should read to unerstand it?

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.
My theory is to just add the PATH (to be changed) to PATH.

Or why don't we auto-compile it and add it (install.scm) to the GUILE_LOAD_PATH?

Anyway I will be experimenting with just this, but answers to these questions
help me to define a better solution.

Thanks!
-- 
ng0
GnuPG: A88C8ADD129828D7EAC02E52E22F9BBFEE348588
GnuPG: https://n0is.noblogs.org/my-keys
https://www.infotropique.org https://krosos.org

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

             reply	other threads:[~2017-08-20 13:44 UTC|newest]

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

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=20170820134425.57ohvu5yy2ux6s2q@abyayala \
    --to=ng0@infotropique.org \
    --cc=guix-devel@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.
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.