From: Tobias Geerinckx-Rice <me@tobias.gr>
To: pkill9@runbox.com
Cc: 34572 <34572@debbugs.gnu.org>
Subject: [bug#34572] Add Drawpile
Date: Thu, 21 Feb 2019 14:58:33 +0100 [thread overview]
Message-ID: <87va1dutti.fsf@nckx> (raw)
In-Reply-To: <E1gwnpA-0005aL-Mm@rmmprod05.runbox>
Pkill -9,
Thanks for this patch, and your many others.
pkill9 wrote:
> + #:use-module (gnu packages crypto) ; libsodium
> + #:use-module (gnu packages gnunet) ; libmicrohttpd
In my experience, what little value such comments add is quickly
lost. Anyone adding new inputs will not update (or even notice)
them.
> + ("giflib" ,giflib) ; optional
> + ("kdnssd" ,kdnssd) ; optional
> + ("miniupnpc" ,miniupnpc) ; optional
> + ("libmicrohttpd" ,libmicrohttpd) ; optional
> + ("libsodium" ,libsodium))) ; optional
Same here: nothing wrong with these, I guess, but *many* package
dependencies are optionally detected at build time and this isn't
usually pointed out unless there's something more interesting
going on.
> + (arguments
> + `(#:configure-flags
> + (list "-DTESTS=on" ; build unit tests.
General remark: no full stop after inline comments.
;; Foo bar.
(foo bar) ; foo bar
> + "-DTOOLS=on" ; build dprec2txt command line tool.
> + (string-append "-DLIBQTCOLORWIDGETS_LIBRARY="
> + (assoc-ref %build-inputs
> "qtcolorwidgets")
> +
> "/lib/libQtColorWidgets-Qt52.so"))))
What about using FIND-FILES "\*.so$" here instead of hard-coding
"52"? Overkill?
Kind regards,
T G-R
next prev parent reply other threads:[~2019-02-21 13:59 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-19 11:59 [bug#34572] Add Drawpile pkill9
2019-02-20 21:01 ` Ricardo Wurmus
2019-02-21 12:51 ` pkill9
2019-02-21 13:58 ` Tobias Geerinckx-Rice [this message]
2019-02-22 7:28 ` pkill9
2021-08-06 4:20 ` bug#34572: " Maxim Cournoyer
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=87va1dutti.fsf@nckx \
--to=me@tobias.gr \
--cc=34572@debbugs.gnu.org \
--cc=pkill9@runbox.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).