all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Vivien Kraus via Bug reports for GNU Guix <bug-guix@gnu.org>
To: 67651@debbugs.gnu.org
Subject: bug#67651: [gnome-team] What should we do with the "gnome" package?
Date: Tue, 05 Dec 2023 21:55:56 +0100	[thread overview]
Message-ID: <271383e7dfc7e1beecc0fcebe533f94e9da4d499.camel@planete-kraus.eu> (raw)

Dear guix,

On the one hand, we have this list of packages:
https://ftp2.nluug.nl/windowing/gnome/teams/releng/44.6/versions

On the other hand, we have the propagated-inputs of the gnome package.

Should we update the latter so that it contains everything from the
former? What should we do about the comments dividing the propagated-
inputs into categories? Where do these categories come from? Should we
preserve them? How do we know which package goes to which category?

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?

Best regards,

Vivien




             reply	other threads:[~2023-12-05 20:57 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-12-05 20:55 Vivien Kraus via Bug reports for GNU Guix [this message]
2023-12-07  7:34 ` bug#67651: [gnome-team] What should we do with the "gnome" package? Liliana Marie Prikler
2023-12-07 11:25 ` Efraim Flashner
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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=271383e7dfc7e1beecc0fcebe533f94e9da4d499.camel@planete-kraus.eu \
    --to=bug-guix@gnu.org \
    --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 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.