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 parent reply other threads:[~2023-12-01 19:59 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <cover.1700321434.git.herman@rimm.ee>
[not found] ` <04c59bffe5d465cb17c0b7e8159642f910ce3f35.1700321434.git.herman@rimm.ee>
2023-12-01 19:58 ` Vagrant Cascadian [this message]
2023-12-03 10:22 ` [bug#67261] [PATCH 3/3] images: Add orangepi-r1-plus-lts image Efraim Flashner
2023-12-22 23:59 ` 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
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=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 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).