unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: Liliana Marie Prikler <liliana.prikler@gmail.com>
To: Vivien Kraus <vivien@planete-kraus.eu>, 51731@debbugs.gnu.org
Subject: bug#51731: [PATCH] gnome-tweaks fails to start on core-updates-frozen
Date: Wed, 10 Nov 2021 18:32:35 +0100	[thread overview]
Message-ID: <73796631dd1dd39a638c948ca3273f5cd3423b88.camel@gmail.com> (raw)
In-Reply-To: <87pmr9x6vu.fsf@planete-kraus.eu>

Hi,

Am Dienstag, den 09.11.2021, 23:10 +0000 schrieb Vivien Kraus:
> I fixed a couple of linter errors, and applied guix style to
> it. However, now the linter complains that we have the "bin" output
> of glib in something that would be called "glib" and not "glib:bin"…
> Should we still keep the styled output?
IIUC that's an issue with the linter or perhaps the implementation of
short input lists in general.  I've CC'd Ludo as he is the one who
allowed us to write inputs (list bash sed ...) in the first place,
perhaps he knows what to do here.  We probably ought to convert this to
short-style inputs anyway.

> Subject: [PATCH 1/5] gnu: gnome-tweaks: Use libhandy 1.
Note, libhandy 0.0 only exists on master (and therefore core-updates),
because there are packages still using it.  If there's no more users
post updating gnome-tweaks, it is to be removed!

> Subject: [PATCH 2/5] gnu: gnome-tweaks: Set the python path.
Nice catch, I think this was previously done by a different phase. 
However...
> gnu/packages/gnome.scm (gnome-tweaks)[phases]: Also wrap with
> GUIX_PYTHONPATH.
Please note the phase and perhaps change its name to reflect what it
does.

> Subject: [PATCH 3/5] gnu: gnome-tweaks: gobject-introspection should
> be a native input.
I'm not sure this is the correct move here.  Python uses GI at runtime,
not natively during build.  If gnome-tweaks requires GI at build time,
it's to be added as both inputs.

> Subject: [PATCH 4/5] gnu: gnome-tweaks: Add bash-minimal as an input
> to wrap the program.
Split the long line.  Also perhaps add a comment in the file itself as
to why this is needed if it's not already obvious from best practises
in core-updates-frozen.

> Subject: [PATCH 5/5] gnu: gnome-tweaks: Style it.
This should probably done first, particularly if it helps avoid the
linter complaints you encounter.

In my personal opinion, 1, 3, 4 and 5 could also be done in a single
commit, though YMMV.  Also, I'm not active on core-updates-frozen, so
take everything I said as lexical analysis at best and with sufficient
amounts of salt.

Cheers,
Liliana





  reply	other threads:[~2021-11-10 17:34 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-11-09 23:10 bug#51731: [PATCH] gnome-tweaks fails to start on core-updates-frozen Vivien Kraus via Bug reports for GNU Guix
2021-11-10 17:32 ` Liliana Marie Prikler [this message]
2021-11-10 20:20   ` Vivien Kraus via Bug reports for GNU Guix
2021-11-11 20:43     ` Liliana Marie Prikler
2021-11-13  9:06       ` Vivien Kraus via Bug reports for GNU Guix
2021-11-15 11:13         ` Ludovic Courtès

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=73796631dd1dd39a638c948ca3273f5cd3423b88.camel@gmail.com \
    --to=liliana.prikler@gmail.com \
    --cc=51731@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).