From: Maxime Devos <maximedevos@telenet.be>
To: Brice Waegeneire <brice@waegenei.re>
Cc: 53953@debbugs.gnu.org
Subject: [bug#53953] [PATCH v2] gnu: Add acpilight.
Date: Sat, 12 Feb 2022 19:05:24 +0100 [thread overview]
Message-ID: <75d1cbd06f8a3a555090de6f698a138631cc04e0.camel@telenet.be> (raw)
In-Reply-To: <20220212172125.3648-1-brice@waegenei.re>
[-- Attachment #1: Type: text/plain, Size: 807 bytes --]
Brice Waegeneire schreef op za 12-02-2022 om 18:21 [+0100]:
> As for the odd make-flags, this is because of the uncanonical Makefile¹ of
> acpilight, It don't build with an empty DESTDIR.
>
> ¹ https://gitlab.com/wavexx/acpilight/-/blob/master/Makefile
Looks like the problem is caused by 'sysconfdir' not being based
on 'prefix', but that can be resolved by
#~(list (string-append "prefix=" #$output)
(string-append "sysconfdir=" (string-append #$output "/etc")))
which is not 100% canonical, but it does seems closer to me?
Also, apparently there's a 'python-minimal' package, so you could use
that instead of 'python' to reduce the closure? Might be counter-
productive though, since most packages seem to use plain 'python'
instead ...
whose closure
would be smaller than
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 260 bytes --]
next prev parent reply other threads:[~2022-02-12 18:06 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-12 10:44 [bug#53953] [PATCH] gnu: Add acpilight Brice Waegeneire
2022-02-12 13:34 ` Maxime Devos
2022-02-12 13:38 ` Maxime Devos
2022-02-12 17:21 ` [bug#53953] [PATCH v2] " Brice Waegeneire
2022-02-12 18:05 ` Maxime Devos [this message]
2022-02-16 7:22 ` [bug#53953] [PATCH v3] " Brice Waegeneire
2022-03-06 21:17 ` [bug#53953] [PATCH] " Ludovic Courtès
2022-04-05 16:06 ` Ludovic Courtès
2022-09-28 19:57 ` bug#53953: " Maxim Cournoyer
2022-06-01 14:14 ` [bug#53953] " Antero Mejr 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=75d1cbd06f8a3a555090de6f698a138631cc04e0.camel@telenet.be \
--to=maximedevos@telenet.be \
--cc=53953@debbugs.gnu.org \
--cc=brice@waegenei.re \
/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).