unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: Efraim Flashner <efraim@flashner.co.il>
To: Vivien Kraus <vivien@planete-kraus.eu>
Cc: 67651@debbugs.gnu.org
Subject: bug#67651: [gnome-team] What should we do with the "gnome" package?
Date: Thu, 7 Dec 2023 13:25:54 +0200	[thread overview]
Message-ID: <ZXGrwiDGiKSPNQu4@3900XT> (raw)
In-Reply-To: <271383e7dfc7e1beecc0fcebe533f94e9da4d499.camel@planete-kraus.eu>

[-- Attachment #1: Type: text/plain, Size: 974 bytes --]

On Tue, Dec 05, 2023 at 09:55:56PM +0100, Vivien Kraus via Bug reports for GNU Guix wrote:
> Dear guix,
>
> The gnome package disables eog on 32-bit machines because it depends on
> librsvg-next. It seems a bit outdated to me, as most of gnome won’t
> work on 32-bit machines, not only eog. Should we try and find which
> ones work on 32-bit systems?

One option would be to wrap everything in 'supported-package?' and
append everything together. Then if something depends on the newer
librsvg and that isn't supported on that architecture it will just be
skipped.

Something to keep in mind though is the rust-team branch adds support
for cross-building rust, so you could end up with a different set of
packages depending on cross-building.

-- 
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 --]

  parent reply	other threads:[~2023-12-07 11:26 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-12-05 20:55 bug#67651: [gnome-team] What should we do with the "gnome" package? Vivien Kraus via Bug reports for GNU Guix
2023-12-07  7:34 ` Liliana Marie Prikler
2023-12-07 11:25 ` Efraim Flashner [this message]
2024-01-07 16:53 ` Liliana Marie Prikler
2024-01-09 11:10   ` Vivien Kraus via Bug reports for GNU Guix
2024-01-09 19:29     ` Liliana Marie Prikler
2024-02-06 17:04 ` Vivien Kraus via Bug reports for GNU Guix

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=ZXGrwiDGiKSPNQu4@3900XT \
    --to=efraim@flashner.co.il \
    --cc=67651@debbugs.gnu.org \
    --cc=vivien@planete-kraus.eu \
    /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).