help-guix
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Access to nongnu channel


From: Timothy Washington
Subject: Re: Access to nongnu channel
Date: Sat, 7 Dec 2024 12:18:08 -0500

Hey Marek,

I should have updated this earlier. But I did solve this problem with a
cleaner `packages` declaration.

(packages
 (append
  (map specification->package
       '("nss-certs"
         "gcc-toolchain"
         ...))
  (list my-package)
  %base-packages))

Thanks for the feedback. Indeed, for me this is an exercise in learning
Guix and developing my understanding of its modules.

Cheers
Tim


On Fri, 6 Dec 2024 at 18:12, Marek Paśnikowski <marek@marekpasnikowski.pl>
wrote:

> 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
>


reply via email to

[Prev in Thread] Current Thread [Next in Thread]