From: Vagrant Cascadian <vagrant@debian.org>
To: Herman Rimm <herman@rimm.ee>, 67261@debbugs.gnu.org
Cc: guix-devel@gnu.org
Subject: Re: [bug#67261] [PATCH 3/3] images: Add orangepi-r1-plus-lts image.
Date: Fri, 01 Dec 2023 11:58:57 -0800 [thread overview]
Message-ID: <87zfytk83i.fsf@wireframe> (raw)
In-Reply-To: <04c59bffe5d465cb17c0b7e8159642f910ce3f35.1700321434.git.herman@rimm.ee>
[-- Attachment #1: Type: text/plain, Size: 847 bytes --]
On 2023-11-18, Herman Rimm wrote:
> * gnu/local.mk: Register image.
> * gnu/system/images/orangepi-r1-plus-lts-rk3328.scm: New file.
> * gnu/system/install.scm (orangepi-r1-plus-lts-rk3328-installation-os):
> New variable.
I guess this opens in my mind a larger question of how many images do we
want to build out-of-the-box?
Building images for every (ARM) board variant possibly supported in guix
might not be sustainable in the long term... this could easily become
hundreds of images. How big is each image?
On the other hand, most of the images for a given architecture will
share much of the work between them, as most of the individual packages
used to build each image are the same.
Not having CI build each and every image is one approach... although
then you might not notice when an individual image breaks.
live well,
vagrant
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 227 bytes --]
next prev parent reply other threads:[~2023-12-01 19:59 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-18 15:38 [bug#67261] [PATCH 0/3] Update u-boot to 2023.10 Herman Rimm via Guix-patches via
2023-11-18 16:01 ` [bug#67261] [PATCH 1/3] gnu: u-boot: Update " Herman Rimm via Guix-patches via
2023-11-24 21:23 ` Vagrant Cascadian
2023-11-18 16:01 ` [bug#67261] [PATCH 2/3] gnu: bootloader: Add orangepi-r1-plus-lts-rk3328 bootloader Herman Rimm via Guix-patches via
2023-12-01 19:50 ` Vagrant Cascadian
2023-11-18 16:01 ` [bug#67261] [PATCH 3/3] images: Add orangepi-r1-plus-lts image Herman Rimm via Guix-patches via
2023-12-01 19:58 ` Vagrant Cascadian [this message]
2023-12-03 10:22 ` Efraim Flashner
2023-12-22 23:59 ` Vagrant Cascadian
2023-11-27 8:33 ` [bug#67261] [PATCH v2] gnu: u-boot: Update to 2023.10 Herman Rimm via Guix-patches via
2023-12-01 19:48 ` Vagrant Cascadian
2023-12-02 7:11 ` Lars-Dominik Braun
2023-12-23 0:19 ` bug#67261: [PATCH 0/3] Update u-boot " Vagrant Cascadian
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=87zfytk83i.fsf@wireframe \
--to=vagrant@debian.org \
--cc=67261@debbugs.gnu.org \
--cc=guix-devel@gnu.org \
--cc=herman@rimm.ee \
/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.