From: phodina via <help-guix@gnu.org>
To: Julien Lepiller <julien@lepiller.eu>
Cc: help-guix <help-guix@gnu.org>, "Ludovic Courtès" <ludo@gnu.org>
Subject: Re: Guix supported-systems option
Date: Sat, 14 Jan 2023 22:01:49 +0000 [thread overview]
Message-ID: <4G3v8WeH2-W4HbzMp6lKpSwRHb4OM6jU91I-gaQUdVgsqfkqWmsCdqSQ6t8bm0a2gDicPTSyy6GO8hjT5Y8Q24bwDbdKKrdpYbjFvoZR9ug=@protonmail.com> (raw)
In-Reply-To: <006ACFAA-0D67-4B5B-9A2B-001A075EAD39@lepiller.eu>
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
next prev parent reply other threads:[~2023-01-14 22:02 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 [this message]
2023-01-14 23:48 ` Julien Lepiller
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='4G3v8WeH2-W4HbzMp6lKpSwRHb4OM6jU91I-gaQUdVgsqfkqWmsCdqSQ6t8bm0a2gDicPTSyy6GO8hjT5Y8Q24bwDbdKKrdpYbjFvoZR9ug=@protonmail.com' \
--to=help-guix@gnu.org \
--cc=julien@lepiller.eu \
--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.
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.