all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Attila Lendvai <attila@lendvai.name>
To: Kyle Andrews <kyle@posteo.net>
Cc: guix-devel@gnu.org
Subject: Re: Help adding a graph backend
Date: Fri, 10 Feb 2023 09:25:10 +0000	[thread overview]
Message-ID: <T3QVRx60O2WL0S_26DSKsLoAnkmMhIhwdc4Hyh0PE0lSKXdzPYf0iz2-OB37qihO0PHSbEUgRXlzLYjAm3kAuy__-6LPcVYt8GplaX3jh50=@lendvai.name> (raw)
In-Reply-To: <87ilga41jh.fsf@posteo.net>

> Since I am not that excited about corrupting my /gnu/store given
> that I don't know what I am doing, I didn't proceed further.

you shouldn't worry until you actually install some packages that you have modified. a subsequent `guix gc` will delete anything you have produced into /gnu/store but haven't installed.

this should work in a git checkout:

guix shell --pure --development guix
./bootstrap
./configure --localstatedir=/var --sysconfdir=/etc
make -j
./pre-inst-env guix graph ...

afterwards you don't need to invoke `make -j` every time you modify something, it just makes the startup time faster.

if you'll ever need to use extra channels and/or packages:

export GUIX_PACKAGE_PATH=/path/to/some-guile-modules:/another/path
export GUILE_LOAD_PATH=/path/to/some-guile-modules:$GUILE_LOAD_PATH

HTH,

-- 
• attila lendvai
• PGP: 963F 5D5F 45C7 DFCD 0A39
--
“The fatal attraction of government is that it allows busybodies to impose decisions on others without paying any price themselves.”
	— Thomas Sowell (1930–)



  parent reply	other threads:[~2023-02-10  9:26 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-10  3:10 Help adding a graph backend Kyle Andrews
2023-02-10  7:11 ` Julien Lepiller
2023-02-10  9:25 ` Attila Lendvai [this message]
2023-02-10  9:30 ` Andreas Enge
2023-02-10 19:03   ` Kyle

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='T3QVRx60O2WL0S_26DSKsLoAnkmMhIhwdc4Hyh0PE0lSKXdzPYf0iz2-OB37qihO0PHSbEUgRXlzLYjAm3kAuy__-6LPcVYt8GplaX3jh50=@lendvai.name' \
    --to=attila@lendvai.name \
    --cc=guix-devel@gnu.org \
    --cc=kyle@posteo.net \
    /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.