From: "Ludovic Courtès" <ludo@gnu.org>
To: Danny Milosavljevic <dannym@scratchpost.org>
Cc: guix-devel@gnu.org
Subject: Re: Importing package-overlay-for-Nix - How?
Date: Wed, 21 Oct 2020 14:59:49 +0200 [thread overview]
Message-ID: <87lffz4tve.fsf@gnu.org> (raw)
In-Reply-To: <20201020104852.26e62055@scratchpost.org> (Danny Milosavljevic's message of "Tue, 20 Oct 2020 10:48:52 +0200")
Hi,
Danny Milosavljevic <dannym@scratchpost.org> skribis:
> How do I use it
>
> guix import nix
>
> in order to import those packages?
This importer has bitrot; it could probably be salvaged with some effort
from someone knowledgeable about today’s Nix (i.e., not me :-)):
https://issues.guix.gnu.org/32339
Another option would be to delete it altogether: it only contributes a
tiny bit to the packaging effort. Only a tiny bit because the difficult
part is written as Bash and/or Nix functions, which the importer cannot
“translate”.
Let’s look at the examples you give:
> https://github.com/librerpi/rpi-open-firmware/blob/master/bcm2835.nix
Could be imported, minus ‘preConfigure’.
> https://github.com/librerpi/rpi-open-firmware/blob/master/bootloader.nix
This is not a package but a NixOS “module” (akin to a Guix service
type).
> https://github.com/librerpi/rpi-open-firmware/blob/master/default.nix
This looks like a package collection (obfuscated, though).
> https://github.com/librerpi/rpi-open-firmware/blob/master/netboot.nix
Not a package but a “module” for a custom initrd.
> https://github.com/librerpi/rpi-open-firmware/tree/master/nix
Not sure what that is.
In short, the importer would save you 2mn of typing for the first file,
little more.
Thanks,
Ludo’.
prev parent reply other threads:[~2020-10-21 13:00 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-20 8:48 Importing package-overlay-for-Nix - How? Danny Milosavljevic
2020-10-21 12:59 ` Ludovic Courtès [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=87lffz4tve.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=dannym@scratchpost.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.