From: soeren@soeren-tempel.net
To: 69962@debbugs.gnu.org
Cc: raghavgururajan@disroot.org, leo@famulari.name
Subject: [bug#69962] [PATCH] gnu: pixman: Disable non-optional verbose gnuplot debugging output
Date: Sat, 23 Mar 2024 12:06:08 +0100 [thread overview]
Message-ID: <a5f579eb754f215c788ec18fba51a10da2c027ef.1711191967.git.soeren@soeren-tempel.net> (raw)
From: Sören Tempel <soeren@soeren-tempel.net>
The --enable-gnuplot option was added previously in Guix Git commit
711316946fa84b55480681588f2cc23811c69784. The option causes any program
linked against the pixman library to constantly write gnuplot input to
standard output. I believe this is not desirable in the common case and,
in fact, this option is intended for testing purposes by upstream [1]. I
don't think that it should be enabled by default in a context of a
distribution.
I noticed this while working porting a Wayland status bar, which uses
pixman, to Guix and wondering why the status bar process was constantly
writing gnuplot input to standard output.
* gnu/packages/xdisorg.scm (pixman): Disable --enable-gnuplot.
[1]: https://gitlab.freedesktop.org/pixman/pixman/-/commit/d0e6c9f4f65e429058b97d2f947b048b445c17c4
---
gnu/packages/xdisorg.scm | 3 +--
1 file changed, 1 insertion(+), 2 deletions(-)
diff --git a/gnu/packages/xdisorg.scm b/gnu/packages/xdisorg.scm
index be8623666f..c85529520d 100644
--- a/gnu/packages/xdisorg.scm
+++ b/gnu/packages/xdisorg.scm
@@ -720,8 +720,7 @@ (define-public pixman
`(#:configure-flags
(list
"--disable-static"
- "--enable-timers"
- "--enable-gnuplot")))
+ "--enable-timers")))
(native-inputs
(list pkg-config))
(inputs
base-commit: f285a968b1219ae748fcab918b17285e741422c2
reply other threads:[~2024-03-23 11:07 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=a5f579eb754f215c788ec18fba51a10da2c027ef.1711191967.git.soeren@soeren-tempel.net \
--to=soeren@soeren-tempel.net \
--cc=69962@debbugs.gnu.org \
--cc=leo@famulari.name \
--cc=raghavgururajan@disroot.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).