bug#67651: closed ([gnome-team] What should we do with the "gnome" package?)

[GNU bug Tracking System]

Your message dated Tue, 06 Feb 2024 18:04:25 +0100
with message-id 
<95ca026b64c7ea0640cbbce7a01363068c8e90b0.camel@planete-kraus.eu>
and subject line [gnome-team] What should we do with the "gnome" package?
has caused the debbugs.gnu.org bug report #67651,
regarding [gnome-team] What should we do with the "gnome" package?
to be marked as done.

(If you believe you have received this mail in error, please contact
help-debbugs@gnu.org.)


-- 
67651: https://debbugs.gnu.org/cgi/bugreport.cgi?bug=67651
GNU Bug Tracking System
Contact help-debbugs@gnu.org with problems
> --- Begin Message ---
>
>
>
> Subject: 
>
> [gnome-team] What should we do with the "gnome" package?
>
>
>
>
> Date: 
>
> Tue, 05 Dec 2023 21:55:56 +0100
>
>
>
>
> User-agent: 
>
> Evolution 3.46.4 
>
>
>
>
> 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
>
>
>
> --- End Message ---
> --- Begin Message ---
>
>
>
> Subject: 
>
> [gnome-team] What should we do with the "gnome" package?
>
>
>
>
> Date: 
>
> Tue, 06 Feb 2024 18:04:25 +0100
>
>
>
>
> User-agent: 
>
> Evolution 3.48.4 
>
>
>
>
> This is being worked on at https://issues.guix.gnu.org/68716
>
>
> --- End Message ---