From: Vagrant Cascadian <vagrant@debian.org>
To: Stefan <stefan-guix@vodafonemail.de>, 48314@debbugs.gnu.org
Cc: Danny Milosavljevic <dannym@scratchpost.org>
Subject: [bug#48314] Patches to install guix system on Raspberry Pi
Date: Sat, 13 Nov 2021 10:23:59 -0800 [thread overview]
Message-ID: <87a6i7c3sw.fsf@ponder> (raw)
In-Reply-To: <AFD31F40-6691-4B53-ACA9-7F821D139124@vodafonemail.de>
[-- Attachment #1: Type: text/plain, Size: 1503 bytes --]
On 2021-10-31, Stefan wrote:
...
Subject: [PATCH 3/8] * gnu/packages/bootloader.scm (make-u-boot-package): Add
keyword parameters 'name' and 'description'.
(make-preinstalled-u-boot-package): New function to make minimal packages.
+(define*-public (make-preinstalled-u-boot-package board
+ triplet
+ #:key
+ defconfig
+ configs
+ name
+ description
+ (u-boot-file "u-boot.bin"))
+ "Returns a package with a single U-BOOT-FILE for BOARD cross-compiled for
+TRIPLET with the optional DEFCONFIG file and optional configuration changes
+from CONFIGS. Either NAME, if used, or otherwise BOARD will be part of the
+package name. DESCRIPTION will be appended to the package description."
u-boot-file appears to be hard-coded; there may be other boards which
use a different u-boot artifact. Also, why return a single file, rather
than just building a package and then allowing other functions to pick
the appropriate file out of the resulting package?
I wondered "why does it have to be cross-compiled" but then realized
that came from the existing make-u-boot-package function. I've mostly
been building u-boot natively these days. :)
live well,
vagrant
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 227 bytes --]
next prev parent reply other threads:[~2021-11-13 18:25 UTC|newest]
Thread overview: 74+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-09 15:32 [bug#48314] Patches to install guix system on Raspberry Pi Stefan
2021-05-16 12:46 ` Stefan
2021-06-19 18:11 ` Danny Milosavljevic
2021-06-19 18:13 ` Danny Milosavljevic
2021-06-19 19:10 ` Stefan
2021-06-19 19:04 ` Danny Milosavljevic
2021-06-19 19:18 ` Stefan
2021-06-19 19:10 ` Danny Milosavljevic
2021-06-19 20:21 ` Stefan
2021-07-28 18:58 ` Stefan
2021-10-31 22:07 ` Stefan
2021-11-13 18:05 ` Vagrant Cascadian
2021-11-13 18:51 ` Vagrant Cascadian
2022-07-17 16:47 ` Stefan via Guix-patches via
2021-11-13 18:23 ` Vagrant Cascadian [this message]
2022-07-17 16:47 ` Stefan via Guix-patches via
2021-11-13 20:21 ` Vagrant Cascadian
2022-07-17 16:47 ` Stefan via Guix-patches via
2022-07-17 17:21 ` Vagrant Cascadian
2022-07-17 18:04 ` Stefan via Guix-patches via
2021-11-17 14:00 ` [bug#48314] Install " phodina via Guix-patches via
2022-04-14 7:38 ` [bug#48314] [PATCH v3] " phodina via Guix-patches via
2022-04-14 8:17 ` phodina via Guix-patches via
2022-04-14 8:32 ` Maxime Devos
2022-04-14 9:25 ` [bug#48314] [PATCH v4] " phodina via Guix-patches via
2022-04-14 11:00 ` Maxime Devos
2022-04-14 12:23 ` [bug#48314] [PATCH v5] " phodina via Guix-patches via
2022-04-14 13:03 ` phodina via Guix-patches via
2022-04-14 13:57 ` Maxime Devos
2022-04-14 14:00 ` Maxime Devos
2022-04-14 14:06 ` [bug#48314] [PATCH v3] " Maxime Devos
2022-04-14 15:53 ` phodina via Guix-patches via
2022-04-14 17:33 ` Maxime Devos
2022-04-15 17:17 ` Ludovic Courtès
2022-04-16 8:53 ` phodina via Guix-patches via
2022-04-18 21:00 ` Ludovic Courtès
2022-04-21 10:52 ` phodina via Guix-patches via
2022-04-21 19:32 ` Stefan
2022-04-14 15:56 ` Vagrant Cascadian
2022-04-28 2:57 ` Vagrant Cascadian
2022-04-28 6:05 ` Stefan
2022-04-28 15:25 ` Vagrant Cascadian
2022-07-02 6:40 ` phodina via Guix-patches via
2022-07-17 16:48 ` Stefan via Guix-patches via
2022-07-17 16:48 ` Stefan via Guix-patches via
2022-07-18 19:23 ` phodina via Guix-patches via
2022-07-19 6:55 ` Stefan via Guix-patches via
2022-07-19 7:35 ` phodina via Guix-patches via
2022-07-20 6:13 ` Stefan via Guix-patches via
2022-07-20 7:16 ` phodina via Guix-patches via
2022-07-20 19:42 ` Stefan via Guix-patches via
2022-08-12 14:27 ` phodina via Guix-patches via
2022-08-13 10:48 ` Stefan via Guix-patches via
2022-08-14 9:59 ` phodina via Guix-patches via
2022-08-14 11:35 ` Stefan via Guix-patches via
2022-09-01 23:55 ` Stefan via Guix-patches via
2022-09-02 5:49 ` phodina via Guix-patches via
2022-09-04 18:41 ` Stefan via Guix-patches via
2022-09-22 16:18 ` [bug#48314] [PATCH v5] " Stefan via Guix-patches via
2022-10-05 13:02 ` Ludovic Courtès
2022-10-08 16:22 ` Vagrant Cascadian
2022-10-09 13:41 ` Stefan via Guix-patches via
2022-10-30 12:39 ` phodina via Guix-patches via
2022-10-30 17:08 ` Stefan via Guix-patches via
2022-10-30 17:31 ` Stefan via Guix-patches via
2022-12-01 14:25 ` [bug#48314] [PATCH] " Maxim Cournoyer
2022-12-01 15:32 ` Maxim Cournoyer
2022-12-01 16:22 ` Maxim Cournoyer
2022-12-01 18:01 ` Maxim Cournoyer
2022-12-01 19:33 ` bug#48314: " Maxim Cournoyer
2022-12-03 5:53 ` [bug#48314] " Vagrant Cascadian
2022-12-04 6:28 ` Maxim Cournoyer
2022-10-30 17:32 ` [bug#48314] [PATCH v5] " Stefan via Guix-patches via
2022-10-30 17:33 ` Stefan via Guix-patches via
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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87a6i7c3sw.fsf@ponder \
--to=vagrant@debian.org \
--cc=48314@debbugs.gnu.org \
--cc=dannym@scratchpost.org \
--cc=stefan-guix@vodafonemail.de \
/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 public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).