From: "Marek Paśnikowski" <marek@marekpasnikowski.pl>
To: help-guix@gnu.org
Subject: Re: Minimal guix build
Date: Sat, 03 Aug 2024 10:06:54 +0200 [thread overview]
Message-ID: <87r0b6ghcx.fsf@marekpasnikowski.pl> (raw)
In-Reply-To: <CANgSNSM=5JfTwGhcSKYk1oAAnUxozeUY1Wot_9pFooUjbY9e+Q@mail.gmail.com> (Kai Jellinghaus's message of "Sun, 21 Jul 2024 21:27:11 +0200")
Kai Jellinghaus <contact@kaij.tech> writes:
> I'm trying to make my own channel & substitution server for x86_64 & armv8.
> Would love to individually scan what packages I really need and only keep
> those around, but can't quite figure out the repo.
>
First, remember that "less is more". What you want to do is excessive
and counter-productive to the goal of learning Guix. My suggestion is to
limit the initial ambition to just replicating the Guix repository in
your network. You may find out it is more complicated than it seems.
After deploying your first channel it is likely that you might be
interested in composing multiple channels with dependencies. I have
observed that only the guix channel is special in a sense that its
modules are accessible from any configuration code without any
preparation. Any other modules almost certainly must be declared as
channel dependencies, like [this][1]:
(channel
(version 0)
(dependencies
(channel
(introduction
(channel-introduction
(version 0)
(commit "897c1a470da759236cc11798f4e0a5f7d4d59fbc")
(signer <<CENSORED>>)))
(name <<CENSORED>>)
(url <<CENSORED>>))
(channel
(introduction
(channel-introduction
(version 0)
(commit "7d17bded11ef1239592e6e5abd40ceee1e99cbb8")
(signer <<CENSORED>>)))
(name <<CENSORED>>)
(url <<CENSORED>>))))
[1]: https://guix.gnu.org/manual/devel/en/html_node/Declaring-Channel-Dependencies.html
prev parent reply other threads:[~2024-08-03 8:07 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-21 19:27 Minimal guix build Kai Jellinghaus
2024-07-26 19:25 ` Leo Famulari
2024-08-03 8:06 ` Marek Paśnikowski [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=87r0b6ghcx.fsf@marekpasnikowski.pl \
--to=marek@marekpasnikowski.pl \
--cc=help-guix@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.