From: Efraim Flashner <efraim@flashner.co.il>
To: Vagrant Cascadian <vagrant@debian.org>
Cc: guix-devel@gnu.org, Herman Rimm <herman@rimm.ee>, 67261@debbugs.gnu.org
Subject: [bug#67261] [PATCH 3/3] images: Add orangepi-r1-plus-lts image.
Date: Sun, 3 Dec 2023 12:22:41 +0200 [thread overview]
Message-ID: <ZWxW8emep1j4BYAD@3900XT> (raw)
In-Reply-To: <87zfytk83i.fsf@wireframe>
[-- Attachment #1: Type: text/plain, Size: 1599 bytes --]
On Fri, Dec 01, 2023 at 11:58:57AM -0800, Vagrant Cascadian wrote:
> 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.
Do we normally build all the images in (gnu system images)? There seems
to be a large number of different file-system offsets needed for
different boards. I suppose we could standardize on a larger size that
would take care of most of them, but until something is setup to make it
possible I'm not sure it's possible to support them for Guix System
without also adding an OS config for the offsets for the root file
system.
--
Efraim Flashner <efraim@flashner.co.il> רנשלפ םירפא
GPG key = A28B F40C 3E55 1372 662D 14F7 41AA E7DC CA3D 8351
Confidentiality cannot be guaranteed on emails sent or received unencrypted
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2023-12-03 10:23 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 ` [bug#67261] [PATCH 3/3] images: Add orangepi-r1-plus-lts image Vagrant Cascadian
2023-12-03 10:22 ` Efraim Flashner [this message]
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=ZWxW8emep1j4BYAD@3900XT \
--to=efraim@flashner.co.il \
--cc=67261@debbugs.gnu.org \
--cc=guix-devel@gnu.org \
--cc=herman@rimm.ee \
--cc=vagrant@debian.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 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).