From: Hartmut Goebel <h.goebel@crazy-compilers.com>
To: Danny Milosavljevic <dannym@scratchpost.org>,
Reza Alizadeh Majd <r.majd@pantherx.org>
Cc: 38926@debbugs.gnu.org
Subject: bug#38926: pcmanfm-qt unable to open files by double click
Date: Tue, 7 Jan 2020 12:19:19 +0100 [thread overview]
Message-ID: <df63a616-0500-185b-4b2a-0d082fb1ce6a@crazy-compilers.com> (raw)
In-Reply-To: <20200105233729.10add7f5@scratchpost.org>
[-- Attachment #1.1: Type: text/plain, Size: 838 bytes --]
Am 05.01.20 um 23:37 schrieb Danny Milosavljevic:
Re. <https://debbugs.gnu.org/cgi/bugreport.cgi?bug=38926>
> No idea how to do that with Qt programs. Hartmut?
For Qt/KDE I did not actually address this topic yet.
I tend to handle this case-by-case: If the coupling is "tight" and if
this is a hard requirement (or a small dependency) I'd substitute the
paths was you suggested. Otherwise I rely on the required package to be
installed my the user or some service definition.
In this special case: To avoid installing all of glib:bin (and thus
glib), we could create a new package "gio-launch-desktop", containing
only this binary.
--
Regards
Hartmut Goebel
| Hartmut Goebel | h.goebel@crazy-compilers.com |
| www.crazy-compilers.com | compilers which you thought are impossible |
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
prev parent reply other threads:[~2020-01-07 11:20 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-04 20:24 bug#38926: pcmanfm-qt unable to open files by double click Reza Alizadeh Majd
2020-01-05 9:56 ` Danny Milosavljevic
2020-01-05 13:52 ` Reza Alizadeh Majd
2020-01-05 22:37 ` Danny Milosavljevic
2020-01-05 22:57 ` Danny Milosavljevic
2020-01-06 10:06 ` Danny Milosavljevic
2020-01-06 16:38 ` Danny Milosavljevic
2020-01-06 16:45 ` Reza Alizadeh Majd
2020-01-06 19:44 ` Danny Milosavljevic
2020-01-07 6:23 ` Reza Alizadeh Majd
2020-01-07 8:03 ` Reza Alizadeh Majd
2020-01-07 11:19 ` Hartmut Goebel [this message]
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=df63a616-0500-185b-4b2a-0d082fb1ce6a@crazy-compilers.com \
--to=h.goebel@crazy-compilers.com \
--cc=38926@debbugs.gnu.org \
--cc=dannym@scratchpost.org \
--cc=r.majd@pantherx.org \
/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).