From: John Kehayias via Bug reports for GNU Guix <bug-guix@gnu.org>
To: Liliana Marie Prikler <liliana.prikler@gmail.com>
Cc: 50789@debbugs.gnu.org, Leo Famulari <leo@famulari.name>
Subject: bug#50789: syncthing-gtk creates autostart file with wrong bin
Date: Mon, 27 Sep 2021 19:04:49 +0000 [thread overview]
Message-ID: <6tbnn-VZChCdcqVZHxISlaQa_4plEwmzKlx8VjXPAR1Eb9br1nNHHryw7o0dgx2o8fVGVVtvNGVeZDiGasd1gqt41dwD7RjULWnR2trcUCE=@protonmail.com> (raw)
In-Reply-To: <e47cb526c42df7fedc22516bfced1c0a998ccc3f.camel@gmail.com>
Hi everyone,
‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐
On Saturday, September 25th, 2021 at 3:02 AM, Liliana Marie Prikler wrote:
> I think the answer to that one is fairly simple. Guix should provide a
> mechanism to generate/link autostart services, ideally via (guix home),
> which will be upstreamed soon (idk if it has one such service already,
> just throwing it out there). However, the preferred solution is to not
> bother with autostart at all and instead use shepherd to manage user
> services – there is a tradeoff to be made between those management
> styles somewhere.
>
I agree we can have a better "Guix way" of doing autostart, documented with examples (perhaps a Cookbook chapter on Desktop usage of Guix). User run shepherd works, at least for some basic background services I run. I don't think it is as documented or as fleshed out as XDG autostart stuff. I too am interested in guix home (just merged!) and will take a look at that.
But back to the matter at hand. Medium to long-term I support better Guix services for autostart, but that doesn't address the problem of having packages run as intended by upstream, at least with reasonable expectations. I think this is expected and reasonable behavior, that a program can create a proper .desktop file in Guix.
Looking at another non-Guix system, the autostart files I have in ~/.confg/autostart mostly (syncthing-gtk being the main exception) use just
Exec=program-name
I see this mostly true for /etc/xdg/autostart as well (non-Guix system). So I think this is an easy and typical behavior we can implement. In this case patching syncthing-gtk to produce Exec=syncthing-gtk. Perhaps upstream would consider it as well, unless they have good reason for a full path here, as opposed to other programs. (Upstream is a bit quiet in activity though.)
What do we think?
John
next prev parent reply other threads:[~2021-09-27 19:05 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-24 21:33 bug#50789: syncthing-gtk creates autostart file with wrong bin John Kehayias via Bug reports for GNU Guix
2021-09-24 22:55 ` Liliana Marie Prikler
2021-09-24 23:15 ` Leo Famulari
2021-09-25 0:45 ` John Kehayias via Bug reports for GNU Guix
2021-09-25 7:02 ` Liliana Marie Prikler
2021-09-27 19:04 ` John Kehayias via Bug reports for GNU Guix [this message]
2021-09-27 21:23 ` Liliana Marie Prikler
2021-09-30 19:29 ` John Kehayias via Bug reports for GNU Guix
2021-09-30 20:00 ` Liliana Marie Prikler
2021-09-30 20:13 ` John Kehayias via Bug reports for GNU Guix
2021-10-01 7:44 ` Liliana Marie Prikler
2022-01-05 19:31 ` John Kehayias via Bug reports for GNU Guix
2022-01-05 21:13 ` Leo Famulari
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='6tbnn-VZChCdcqVZHxISlaQa_4plEwmzKlx8VjXPAR1Eb9br1nNHHryw7o0dgx2o8fVGVVtvNGVeZDiGasd1gqt41dwD7RjULWnR2trcUCE=@protonmail.com' \
--to=bug-guix@gnu.org \
--cc=50789@debbugs.gnu.org \
--cc=john.kehayias@protonmail.com \
--cc=leo@famulari.name \
--cc=liliana.prikler@gmail.com \
/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).