[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Access to nongnu channel
From: |
Marek Paśnikowski |
Subject: |
Re: Access to nongnu channel |
Date: |
Sat, 07 Dec 2024 00:11:28 +0100 |
On poniedziałek, 2 grudnia 2024 15:58:31 CET Timothy Washington wrote:
> => However, I seem to get further along when I specify "channels.scm".
> After adding "(guix profiles)" to the "use-modules" in system.scm...
>
> (use-modules (gnu)
> (nongnu packages linux)
> (guix profiles))
>
>
> I get a bit further, where guix can't find another form... *Which package
> has "manifest->packages" ?*
>
> $ guix pull --channels=channels.scm
> ...
>
> $ guix system reconfigure system.scm
> /home/twashing/dotfiles/system.scm:36:6: error: manifest->packages: unbound
> variable
> hint: Did you forget a `use-modules' form?
>
You have to learn to recognize this class of error. It means you failed to
specify the module containing the definition of (manifest->packages) function.
I do not use it myself, so I don’t know where it is defined.
Also, your package list construction is clunky and round-about. I recommend
taking a look at specification->package+output, if I recall correctly, at
least. I have had no issues with listing package variables directly.
I am still in the process of refactoring my module collection, but take a look
at this file in particular to see a very different style of programming Guix.
You are free to browse the other files for more inspiration, but be warned not
to replicate the (@ (module) variable) syntax — it ended up backfiring in a
most subtle of ways, and now I am undoing weeks of work to remove it.
Marek Pasnikowski
signature.asc
Description: This is a digitally signed message part.