From: John Kehayias via Guix-patches via <guix-patches@gnu.org>
To: Hilton Chain <hako@ultrarare.space>
Cc: 75337-done@debbugs.gnu.org, collin@rekahsoft.ca
Subject: bug#75337: [PATCH 0/2] Add hyprland-qtutils; use it Hyprland
Date: Mon, 06 Jan 2025 19:37:11 +0000 [thread overview]
Message-ID: <87o70jka3i.fsf@protonmail.com> (raw)
In-Reply-To: <87o70mmxr9.wl-hako@ultrarare.space>
Hi,
On Sat, Jan 04, 2025 at 10:58 PM, Hilton Chain wrote:
> On Sat, 04 Jan 2025 13:23:05 +0800,
> John Kehayias wrote:
>> One thing to point out is that I manually wrapped the binaries with needed QT
>> environment variables to get them to work. Using qt-buid-system or calling
>> qt-wrap-program (or qt-wrap-all-programs) did not do much: it just added the
>> plugin path for qtbase-5 (not an input here). I didn't try to investigate
>> further but maybe the qt-team could chime in.
>
> qt-build-system has a #:qtbase argument, you can set it to qtbase.
>
Right, and I swear I tried that but I guess that's what happens when
you do a bunch of things at the same time late at night :) Or maybe it
was when I was just using the wrap-qt-program phase and didn't quite
do it correctly. Anyway, that does indeed work and is much cleaner
now.
>> On the Hyprland end, it just checks for these utlities somewhere on the PATH
>> (or something like that) so I just used propagated-inputs. The package/build
>> does not otherwise depend or try to find these at build time. Using
>> propagated-inputs seems to me the easiest and most straight forward method
>> here (the source does not just hardcode something like
>> "/usr/bin/hyprland-dialog" to patch with a store path).
>
> Found a pattern to bypass the check :)
> --8<---------------cut here---------------start------------->8---
> (substitute* ...
> (("!executableExistsInPath.*\".") "false")
> (("hyprland-update-screen" cmd)
> (search-input-file inputs (in-vicinity "bin" cmd))))
> --8<---------------cut here---------------end--------------->8---
>
Ah nice, thanks! I used that and made hyprland-qtutils just a regular
input (after checking the substitutions were correct in both files and
searching Hyprland to make sure that there were no other instances). I
added you as co-author to that patch.
Pushed both, as 8f261686ec0e5a988935e76e5495898e036f9fa7 and
0b4b22b6d363d0dd0bdaee65e47bda5cac72475c
Thanks for the help!
John
prev parent reply other threads:[~2025-01-06 19:38 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-04 5:23 [bug#75337] [PATCH 0/2] Add hyprland-qtutils; use it Hyprland John Kehayias via Guix-patches via
2025-01-04 5:25 ` [bug#75337] [PATCH 1/2] gnu: Add hyprland-qtutils John Kehayias via Guix-patches via
2025-01-04 5:26 ` [bug#75337] [PATCH 2/2] gnu: hyprland: Add hyprland-qtutils to propagated-inputs John Kehayias via Guix-patches via
2025-01-04 14:58 ` [bug#75337] [PATCH 0/2] Add hyprland-qtutils; use it Hyprland Hilton Chain
2025-01-06 19:37 ` John Kehayias via Guix-patches via [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=87o70jka3i.fsf@protonmail.com \
--to=guix-patches@gnu.org \
--cc=75337-done@debbugs.gnu.org \
--cc=collin@rekahsoft.ca \
--cc=hako@ultrarare.space \
--cc=john.kehayias@protonmail.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).