From: Zhu Zihao <all_but_last@163.com>
To: Mark H Weaver <mhw@netris.org>
Cc: 45193@debbugs.gnu.org
Subject: bug#45193: Wrapper of Qt programs doesn't extend existing environment variable
Date: Thu, 17 Dec 2020 19:35:43 +0800 [thread overview]
Message-ID: <86mtycbr74.fsf@163.com> (raw)
In-Reply-To: <87im94ru9t.fsf@netris.org>
[-- Attachment #1: Type: text/plain, Size: 833 bytes --]
I try to read and understand how wrap-qt-program in qt-utils.scm works.
When building QT program, Guix builder populates qt related environment
variable, and wrap-qt-program just record it into wrapper.
However, the wrap behaviour in qt-build-system is quite different, it
search all inputs and mark them should be included in envvar definition
if correspond directory exists.
Another difference is, wrap-qt-program will include the directory of
output in envvar but qt-build-system won't do.
I'm not sure whether we need to include output, and don't know recording
build time environment follows reproducible build rule or not. Maybe we
need an expert on Qt programming/packaging to give us some hints? :(
--
Retrieve my PGP public key:
gpg --recv-keys D47A9C8B2AE3905B563D9135BE42B352A9F6821F
Zihao
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 255 bytes --]
next prev parent reply other threads:[~2020-12-17 11:44 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-12 9:11 bug#45193: Wrapper of Qt programs doesn't extend existing environment variable Zhu Zihao
[not found] ` <handler.45193.B.160776432713396.ack@debbugs.gnu.org>
2020-12-12 9:19 ` bug#45193: Acknowledgement (Wrapper of Qt programs doesn't extend existing environment variable) Zhu Zihao
2020-12-14 20:45 ` bug#45193: Wrapper of Qt programs doesn't extend existing environment variable Mark H Weaver
2020-12-15 1:50 ` Zhu Zihao
2020-12-17 11:35 ` Zhu Zihao [this message]
2020-12-19 13:13 ` Hartmut Goebel
2020-12-19 18:20 ` Zhu Zihao
2020-12-19 19:12 ` Hartmut Goebel
2021-01-10 16:34 ` Zhu Zihao
2021-01-11 8:17 ` Hartmut Goebel
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=86mtycbr74.fsf@163.com \
--to=all_but_last@163.com \
--cc=45193@debbugs.gnu.org \
--cc=mhw@netris.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 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.