From: John Kehayias <john.kehayias@protonmail.com>
To: "guix-devel@gnu.org" <guix-devel@gnu.org>
Cc: "maximedevos@telenet.be" <maximedevos@telenet.be>
Subject: Re: avoid wrapper scripts when possible
Date: Fri, 24 Sep 2021 21:38:11 +0000 [thread overview]
Message-ID: <LOrXk4FVx27Y48NtszaaClH8HBTI7QwawSB9W0MPQyP6rIzcHGq_ALpe25xsOiWqBXU-4szeGlLSkniehHsiFHr4E5H0wasls5xcHrOOWag=@protonmail.com> (raw)
Related is #50798 which I just filed https://debbugs.gnu.org/cgi/bugreport.cgi?bug=50789 This is a similar issue in the executable path picked up by a program (finding the -real one) and using that for writing a .desktop file.
Not sure if there is anything more general to do here, other than having to find these cases and patch manually? Is there a preferred way of making these patches?
Thanks,
John
next reply other threads:[~2021-09-24 21:38 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-24 21:38 John Kehayias [this message]
-- strict thread matches above, loose matches on Subject: below --
2021-09-07 18:52 avoid wrapper scripts when possible Attila Lendvai
2021-09-07 20:41 ` Maxime Devos
2021-09-08 9:20 ` Attila Lendvai
2021-09-08 10:39 ` Maxime Devos
2017-11-02 21:31 Ricardo Wurmus
2017-11-03 18:54 ` Christopher Baines
2017-11-03 19:22 ` Jan Nieuwenhuizen
2017-11-03 21:17 ` Ricardo Wurmus
[not found] ` <874lqbghlz.fsf@elephly.net>
2017-11-03 22:41 ` Ricardo Wurmus
2017-11-05 11:10 ` Hartmut Goebel
2017-11-04 21:42 ` Eric Bavier
2017-11-04 10:12 ` Hartmut Goebel
[not found] ` <87tvy9ptge.fsf@elephly.net>
2017-11-05 11:00 ` Hartmut Goebel
2017-11-05 17:06 ` Ludovic Courtès
2017-11-06 15:53 ` Dave Love
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='LOrXk4FVx27Y48NtszaaClH8HBTI7QwawSB9W0MPQyP6rIzcHGq_ALpe25xsOiWqBXU-4szeGlLSkniehHsiFHr4E5H0wasls5xcHrOOWag=@protonmail.com' \
--to=john.kehayias@protonmail.com \
--cc=guix-devel@gnu.org \
--cc=maximedevos@telenet.be \
/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).