From: Hilton Chain <hako@ultrarare.space>
To: John Kehayias <john.kehayias@protonmail.com>
Cc: 75337@debbugs.gnu.org, collin@rekahsoft.ca
Subject: [bug#75337] [PATCH 0/2] Add hyprland-qtutils; use it Hyprland
Date: Sat, 04 Jan 2025 22:58:34 +0800 [thread overview]
Message-ID: <87o70mmxr9.wl-hako@ultrarare.space> (raw)
In-Reply-To: <cover.1735967250.git.john.kehayias@protonmail.com>
On Sat, 04 Jan 2025 13:23:05 +0800,
John Kehayias wrote:
>
> Hi all,
>
> As pointed out in <https://issues.guix.gnu.org/75036#2>, Hyprland now wants
> binaries from the hyprland-qtutils package, which this patch series adds. I
> checked that it builds and I can run the utlities. One is to send a message if
> Hyprland is updated, which isn't relevant for our package, but I didn't look
> into any easy way to disable that from the source if that's what we want to
> do.
>
> 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.
> 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---
> I have not actually tried running the latest Hyprland which will warn (but
> otherwise should work) about these.
>
> Thanks all!
> John
>
> John Kehayias (2):
> gnu: Add hyprland-qtutils.
> gnu: hyprland: Add hyprland-qtutils to propagated-inputs.
>
> gnu/packages/qt.scm | 55 +++++++++++++++++++++++++++++++++++++++++++++
> gnu/packages/wm.scm | 2 ++
> 2 files changed, 57 insertions(+)
>
>
> base-commit: a707ebe5d3875a49523bc17de2d36af6f1c18f7e
> prerequisite-patch-id: 3efc585c869da704ca71214328a78b6e6bbad919
> prerequisite-patch-id: 82bcb22fe1f5bd69d26626e575b7629f6f223ae3
> prerequisite-patch-id: b12f224a58be29cf89415a53dc245e4057139e22
> prerequisite-patch-id: 9fa5469aa4528c28962598256414bf4a4f517dce
> --
> 2.47.1
>
>
next prev parent reply other threads:[~2025-01-04 15:41 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 ` Hilton Chain [this message]
2025-01-06 19:37 ` bug#75337: [PATCH 0/2] Add hyprland-qtutils; use it Hyprland John Kehayias via Guix-patches via
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=87o70mmxr9.wl-hako@ultrarare.space \
--to=hako@ultrarare.space \
--cc=75337@debbugs.gnu.org \
--cc=collin@rekahsoft.ca \
--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).