unofficial mirror of guix-patches@gnu.org 
 help / color / mirror / code / Atom feed
From: "Ludovic Courtès" <ludo@gnu.org>
To: Mathieu Othacehe <othacehe@gnu.org>
Cc: 45020@debbugs.gnu.org
Subject: [bug#45020] [PATCH 0/2] image: Add system field.
Date: Fri, 11 Dec 2020 17:50:48 +0100	[thread overview]
Message-ID: <87eejw5lsn.fsf@gnu.org> (raw)
In-Reply-To: <20201203105353.149482-1-othacehe@gnu.org> (Mathieu Othacehe's message of "Thu, 3 Dec 2020 11:53:51 +0100")

Hi!

Mathieu Othacehe <othacehe@gnu.org> skribis:

> Here's a small patchset to improve the creation of disk-images on non-Intel
> systems. Currently, when selecting "arm32-raw" or "arm64-raw" image types,
> "guix system" will try to cross-compile to the relevant architectures,
> regardless of the current system architecture.
>
> This adds a "system" field to the image definition that indicates the
> appropriate system. Then, if we are already running on this system,
> "system-image" will build the image natively instead of using
> cross-compilation. The image type "raw" is also renamed to "efi-raw" which is
> more accurate.
>
> Finally, as discussed with Danny on IRC, it could make sense to change the
> default image type depending on the current system: efi-raw on x86_64-linux
> and i686-linux, arm32-raw on armhf-linux and so on.

I understand the need for an easier way to create images.  However, I
feel like <image> is the wrong place for ‘system’ and ‘target’: the
image format, conceptually, has nothing to do with whether we’re
cross-compiling, compiling for a specific system, etc.

It also seems wrong to me that ‘--image-type’ would, in some cases (but
not all?), override ‘-s’ and ‘--target’.

I feel like we’re missing an abstraction that would build on top of
images, but I’m not sure what that would look like.

Thoughts?

Ludo’.




  parent reply	other threads:[~2020-12-11 16:52 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-12-03 10:53 [bug#45020] [PATCH 0/2] image: Add system field Mathieu Othacehe
2020-12-03 10:53 ` [bug#45021] [PATCH 1/2] " Mathieu Othacehe
2020-12-03 20:41   ` Danny Milosavljevic
2020-12-04  8:12     ` Mathieu Othacehe
2020-12-04  9:01       ` Danny Milosavljevic
2020-12-05 10:24         ` Mathieu Othacehe
2020-12-03 10:53 ` [bug#45022] [PATCH 2/2] image: Rename "raw" image-type to "efi-raw" Mathieu Othacehe
2020-12-03 13:11 ` [bug#45020] [PATCH 0/2] image: Add system field zimoun
2020-12-09  8:25 ` Efraim Flashner
2020-12-09 10:15   ` Mathieu Othacehe
2020-12-09 10:27     ` Efraim Flashner
2020-12-11 16:50 ` Ludovic Courtès [this message]
2020-12-12  8:30   ` Mathieu Othacehe
2020-12-12 12:34     ` zimoun
2020-12-13 14:15       ` Ludovic Courtès
2020-12-15 14:11         ` zimoun
2020-12-15 21:56           ` Ludovic Courtès
2020-12-12 17:51     ` Ludovic Courtès
2020-12-15  9:58       ` Mathieu Othacehe
2021-07-16  2:04         ` Maxim Cournoyer
2021-08-30 16:24           ` Mathieu Othacehe
2021-10-05  8:26             ` Mathieu Othacehe
2021-10-11 12:06               ` bug#45020: " Mathieu Othacehe
2020-12-13 14:59     ` [bug#45020] " Danny Milosavljevic

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=87eejw5lsn.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=45020@debbugs.gnu.org \
    --cc=othacehe@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 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).