From: Maxime Devos <maximedevos@telenet.be>
To: derekchuank@outlook.com, 55769@debbugs.gnu.org
Subject: [bug#55769] [PATCH] gnu: Add xwhite.
Date: Thu, 02 Jun 2022 20:43:33 +0200 [thread overview]
Message-ID: <2944e4aeb64f24e053e972440b2649333679cc9a.camel@telenet.be> (raw)
In-Reply-To: <TYCP286MB1123CECB77358C7315CAE47ABEDE9@TYCP286MB1123.JPNP286.PROD.OUTLOOK.COM>
[-- Attachment #1: Type: text/plain, Size: 2038 bytes --]
derekchuank@outlook.com schreef op do 02-06-2022 om 15:39 [+0000]:
> + (arguments
> + `(#:tests? #f
Always add a comment on why tests are disabled.
In this case, probably because there are no tests?
> + #:phases
> + (modify-phases %standard-phases
> + (delete 'configure)
> + (replace 'install
> + (lambda* (#:key outputs #:allow-other-keys)
> + (let ((out (assoc-ref outputs "out")))
> + (install-file "xwhite" (string-append out "/bin"))
> + #t))))))
Trailing #t haven't been necessary anymore since a long time
Also, a comment on the makefile. In the makefile you do CC=gcc, but
that won't work when cross-compiling, because then TARGET-gcc (e.g.
aarch64-linux-gnu-gcc) is required. There are multiple ways to resolve
this, but given that you are upstream, I recommend switching to a build
system such as, say, meson[0]. meson (and autotools) take care of such
details for you (cross-compilation, also choosing the right
installation directory).
If you use meson or autotools, then you won't have to add any Guix
phases or do cross-compilation detection in the makefile, you then only
have to replace gnu-build-system by
meson-build-system.
A comment on the license: strictly speaking, you have licensed it as
‘any version of the GPL whatsoever’. From the GPL itself:
> If the Program does not specify a version number of this License, you
> may choose any version ever published by the Free Software
> Foundation.
I doubt that's what you mean, so maybe document it in the README to be
GPL-2-or-later or GPL-2-only or GPL-2-OR-3-only?
A comment on the code itself: I recommend returning a non-zero value on
failure. Also, all this is already implemented by another tool:
$ redshift -P -g 2:2:0.1 -O 10000
so to me there appears to be no need to write, maintain and package a
new tool.
[0] https://mesonbuild.com/
Greetings,
Maxime
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 260 bytes --]
next prev parent reply other threads:[~2022-06-02 18:44 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-02 15:39 [bug#55769] [PATCH] gnu: Add xwhite derekchuank
2022-06-02 18:43 ` Maxime Devos [this message]
2022-06-03 19:07 ` derekchuank
2022-06-03 19:32 ` Maxime Devos
2022-06-07 16:28 ` bug#55769: " Ludovic Courtès
[not found] <TYCP286MB112305E6ECC94C4EB64342D7BEA19@TYCP286MB1123.JPNP286.PROD.OUTLOOK.COM>
2022-06-03 13:13 ` [bug#55769] " Maxime Devos
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=2944e4aeb64f24e053e972440b2649333679cc9a.camel@telenet.be \
--to=maximedevos@telenet.be \
--cc=55769@debbugs.gnu.org \
--cc=derekchuank@outlook.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).