From: Miguel Arruga Vivas <rosen644835@gmail.com>
To: Kei Kebreau <kkebreau@posteo.net>
Cc: guix-devel@gnu.org
Subject: Re: 'core-updates' Q4 2019
Date: Mon, 4 Nov 2019 20:37:59 +0100 [thread overview]
Message-ID: <20191104203646.4181f4ca@gmail.com> (raw)
In-Reply-To: <875zk3ui5p.fsf@posteo.net>
Hi Kei,
Kei Kebreau <kkebreau@posteo.net> writes:
> Update: Please check out the new wip-gnome-updates branch of the Guix
> git repository for continued updates. The contents of the notabug.org
> link given above will be changed to a notice that says to do this.
Thank you very much for this huge effort. I've been playing with the
branch and I have a working system, both X11 with GDM and Wayland with
SDDM (I haven't tried hard enough to set up gdm with wayland as only a
change to gdm-configuration doesn't seem to have any effect) and your
branch works great on my machine, do you still have the issue during
boot? I haven't found any (new) problem on the applications I've
tested (x86_64, normal use with almost all of the gnome applications,
not the games though.)
Nevertheless, I've been reading the patches and I have a couple of
comments about them:
- The patch for libdazzle only changes the xorg-server, as it already
is at version 3.33.90 in master. It still makes sense as a patch,
but the title indicates a version downgrade.
- The patch for gedit contains a reference to libgd, wouldn't it be
clearer for the reader/updater to have it defined in a let over the
package definition and use the name in native-inputs?
- Is there any reason to not patch-out the gtk-icon-update-cache
invocations? If I understand it correctly, this is performed at
profile level, so makes no sense creating a cache at package level,
isn't it? The patches for quadrapassel, gnome-klotski, ghex,
gnome-sudoku, gnome-mines, five-or-more and gedit contain references
to it. Maybe creating a package like xorg-server-for-tests
(perhaps 'gtk-bin-for-build'?) linked to "true" from coreutils would
help in the long term.
As a final comment, the gnome release cycle and the amount of packages
involved is quite big, so again, thank you.
Happy hacking!
Miguel
next prev parent reply other threads:[~2019-11-04 19:43 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-08 21:55 'core-updates' Q4 2019 Marius Bakke
2019-10-09 11:53 ` Mathieu Othacehe
2019-10-10 14:32 ` Ludovic Courtès
2019-10-10 15:35 ` Mathieu Othacehe
2019-10-10 21:22 ` Svante Signell
2019-10-11 7:52 ` Ludovic Courtès
2019-10-11 20:42 ` Kei Kebreau
2019-10-12 22:15 ` Ludovic Courtès
2019-10-15 1:28 ` Kei Kebreau
2019-10-15 16:49 ` Marius Bakke
2019-10-17 20:44 ` Kei Kebreau
2019-10-17 21:29 ` Ricardo Wurmus
2019-10-18 1:53 ` Kei Kebreau
2019-10-18 3:08 ` Ricardo Wurmus
2019-10-19 13:34 ` Timothy Sample
2019-10-20 3:29 ` Kei Kebreau
2019-10-21 13:58 ` pelzflorian (Florian Pelz)
2019-10-22 0:37 ` Timothy Sample
2019-10-23 3:07 ` Timothy Sample
2019-10-23 7:49 ` pelzflorian (Florian Pelz)
2019-10-26 20:26 ` Kei Kebreau
2019-10-23 17:49 ` Marius Bakke
2019-10-24 2:07 ` Timothy Sample
2019-10-24 18:17 ` Marius Bakke
2019-10-26 21:25 ` Timothy Sample
2019-11-02 2:27 ` Kei Kebreau
2019-11-04 19:37 ` Miguel Arruga Vivas [this message]
2019-11-05 23:38 ` Kei Kebreau
2019-11-06 17:46 ` Leo Famulari
2019-11-07 1:16 ` Kei Kebreau
2019-11-07 2:58 ` Timothy Sample
2019-11-08 0:58 ` Miguel Arruga Vivas
2019-11-23 2:11 ` Kei Kebreau
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=20191104203646.4181f4ca@gmail.com \
--to=rosen644835@gmail.com \
--cc=guix-devel@gnu.org \
--cc=kkebreau@posteo.net \
/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).