From: Tobias Geerinckx-Rice <me@tobias.gr>
To: Jesse Gibbons <jgibbons2357@gmail.com>
Cc: guix-devel@gnu.org
Subject: Re: Is using xdg-utils post-install safe?
Date: Mon, 28 Oct 2019 20:12:34 +0100 [thread overview]
Message-ID: <87blu0zntp.fsf@nckx> (raw)
In-Reply-To: <11ed87ea281954cef56a0f703ade801f80301452.camel@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1165 bytes --]
Jesse,
Jesse Gibbons 写道:
> I'm working on packaging The Powder Toy. When it first starts,
> it asks if
> the user wants to install it.
‘Install’? That doesn't sound good. :-)
<https://github.com/The-Powder-Toy/The-Powder-Toy/blob/master/src/client/Client.cpp#L366>.
From my reading, that will embed a store file name into a .desktop
file somewhere in (each) user's $HOME, which will break sooner or
later.
> When the user clicks confirm, it tries to use
> xdg-desktop-menu, xdg-mime, and xdg-icon-resource.
> Is this a safe behavior with guix, or should I try to patch it
> out?
> If it is safe, should I bother trying to install a desktop icon
> with guix if
> the program will do that itself?
Even if I'm wrong and it's ‘safe’, I don't see how this behaviour
is desirable. What is upstream trying to accomplish here? Do you
see how this would be helpful compared to doing things the
normally?
If not, I think we have a responsibility towards our users to
install a copy of the above .desktop file and patch out any
xdg-desktop-menu calls. Same for MIME types and icons.
Kind regards,
T G-R
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 832 bytes --]
next prev parent reply other threads:[~2019-10-28 19:13 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-28 15:18 Is using xdg-utils post-install safe? Jesse Gibbons
2019-10-28 19:12 ` Tobias Geerinckx-Rice [this message]
2019-10-29 0:09 ` Jesse Gibbons
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87blu0zntp.fsf@nckx \
--to=me@tobias.gr \
--cc=guix-devel@gnu.org \
--cc=jgibbons2357@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 external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.