From: Maxim Cournoyer <maxim.cournoyer@gmail.com>
To: Leo Prikler <leo.prikler@student.tugraz.at>
Cc: 35594@debbugs.gnu.org, 36376@debbugs.gnu.org
Subject: bug#35594: bug#36376: Application menu of desktop environment not automatically updated
Date: Wed, 04 Nov 2020 16:41:58 -0500 [thread overview]
Message-ID: <87v9ekyf2x.fsf@gmail.com> (raw)
In-Reply-To: <63d4101b796673602872997b7680d6b04a189de3.camel@student.tugraz.at> (Leo Prikler's message of "Wed, 04 Nov 2020 00:28:51 +0100")
Hello Ludovic and Leo,
Leo Prikler <leo.prikler@student.tugraz.at> writes:
> Hi Ludo,
>
> Am Dienstag, den 03.11.2020, 23:46 +0100 schrieb Ludovic Courtès:
>> Ludovic Courtès <ludo@gnu.org> skribis:
>>
>> > This is not news to us, but as
>> > <https://distrowatch.com/weekly.php?issue=20190624#guixsd> notes,
>> > the
>> > application menu of desktop environments is not automatically
>> > updated
>> > when a package is installed or removed. It’d be great if we could
>> > somehow notify the desktop environment.
>>
>> We’ve investigated today on IRC with Maxim and Leo P. and here’s the
>> summary of our findings:
> Seeing my name thrown around more and more lately makes me blush a
> little.
>> [...]
>>
>> The GLib patch below is an attempt to monitor ~/.guix-profile and to
>> treat changes to that symlink as if they were changes to
>> ~/.guix-profile/share/applications (which contains ‘.desktop’ files.)
>> It actually builds but I haven’t tested it yet. :-)
>>
>> WDYT?
Pretty cool! It'd keep on working even if we even clean up /etc/profile
from the hardcoded defauts environment variables (say, if we merge one
of the proposed solution of https://issues.guix.gnu.org/22138).
> Not having tested it either, I think that we should also listen on
> /run/current-system/ (if it exists), so that changes to the system as
> done by `reconfigure` are picked up. This includes most importantly
> changes to the GNOME ecosystem itself.
I agree that it seems useful and important to add a monitor on the
/run/current-system as well.
Thank you!
Maxim
next prev parent reply other threads:[~2020-11-04 21:43 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-25 14:12 bug#36376: Application menu of desktop environment not automatically updated Ludovic Courtès
2020-11-03 22:46 ` Ludovic Courtès
2020-11-03 23:28 ` Leo Prikler
2020-11-04 21:41 ` Maxim Cournoyer [this message]
2020-11-04 22:15 ` Ludovic Courtès
2020-11-05 6:38 ` Maxim Cournoyer
2020-11-06 16:02 ` Ludovic Courtès
2020-11-06 18:56 ` Maxim Cournoyer
2020-11-10 15:23 ` Ludovic Courtès
2020-11-10 17:48 ` bug#35594: " zimoun
2020-11-10 21:23 ` Ludovic Courtès
2020-11-12 15:56 ` bug#35594: " Ludovic Courtès
2020-11-13 20:38 ` bug#36376: " Ludovic Courtès
2020-11-17 4:57 ` Maxim Cournoyer
2020-11-17 9:08 ` Ludovic Courtès
2020-11-18 4:34 ` Maxim Cournoyer
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=87v9ekyf2x.fsf@gmail.com \
--to=maxim.cournoyer@gmail.com \
--cc=35594@debbugs.gnu.org \
--cc=36376@debbugs.gnu.org \
--cc=leo.prikler@student.tugraz.at \
/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).