unofficial mirror of help-guix@gnu.org 
 help / color / mirror / Atom feed
From: Julien Lepiller <julien@lepiller.eu>
To: phodina <phodina@protonmail.com>
Cc: help-guix <help-guix@gnu.org>, "Ludovic Courtès" <ludo@gnu.org>
Subject: Re: Guix supported-systems option
Date: Sun, 15 Jan 2023 00:48:06 +0100	[thread overview]
Message-ID: <668F4FF9-FFB1-4D6D-923C-5C81D76EA355@lepiller.eu> (raw)
In-Reply-To: <4G3v8WeH2-W4HbzMp6lKpSwRHb4OM6jU91I-gaQUdVgsqfkqWmsCdqSQ6t8bm0a2gDicPTSyy6GO8hjT5Y8Q24bwDbdKKrdpYbjFvoZR9ug=@protonmail.com>

That's how it's done with some packages that need arch-specific things (inputs, build phases, …) so yes :)

Le 14 janvier 2023 23:01:49 GMT+01:00, phodina <phodina@protonmail.com> a écrit :
>Hi Julien,
>
>> I think you have multiple packages with the same name and version, but different supported systems. Am I right?
>
>you are correct. I have multiple package definitions as shown in the attached scheme file.
>
>The names and versions are exactly the same, just the origin differs and Guix picks "randomly" one of them.
>
>I did as you suggested to rename the packages - append the arch. This works in short term but I'd like to have one profile and just apply it on my laptop (x86_64) as well as on Raspberry Pi (aarch64, recently added to Guix by Stefan).
>
>Having different names will then not work or results in even bigger mess with if statements.
>
>> Now, supported-systems does not mean "remove this package on other architectures", but rather "can't build this on other architectures". So it's perfectly possible that guix will arbitrarily select a package for a different architecture.
>
>Well this is the reason I ask. I though this has deeper meaning as to tell Guix, okay you found a package with that name, but it's not for current architecture. So keep looking and if you don't find any other return this one with a warning that it's not supported.
>
>So the "right" way would be conditionally select the right origin for the package and use just one package definition with list of supported systems, right?
>
>----
>Petr

      reply	other threads:[~2023-01-14 23:49 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-14 19:33 Guix supported-systems option phodina via
2023-01-14 20:19 ` Julien Lepiller
2023-01-14 22:01   ` phodina via
2023-01-14 23:48     ` Julien Lepiller [this message]

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=668F4FF9-FFB1-4D6D-923C-5C81D76EA355@lepiller.eu \
    --to=julien@lepiller.eu \
    --cc=help-guix@gnu.org \
    --cc=ludo@gnu.org \
    --cc=phodina@protonmail.com \
    /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.
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).