From: Nicolas Goaziou <mail@nicolasgoaziou.fr>
To: Leo Famulari <leo@famulari.name>
Cc: 52875@debbugs.gnu.org
Subject: [bug#52875] [PATCH] gnu: Add musikcube.
Date: Thu, 30 Dec 2021 00:13:49 +0100 [thread overview]
Message-ID: <878rw380nm.fsf@nicolasgoaziou.fr> (raw)
In-Reply-To: <8fe1260a15b00246f3987bb58dc1189fb07561f6.1640798010.git.leo@famulari.name> (Leo Famulari's message of "Wed, 29 Dec 2021 12:13:30 -0500")
Hello,
Leo Famulari <leo@famulari.name> writes:
> * gnu/packages/music.scm (musikcube): New variable.
Nice! Thanks.
> +(define-public musikcube
> + (package
> + (name "musikcube")
> + (version "0.96.10")
> + (source (origin
> + (method git-fetch)
> + (uri (git-reference
> + (url "https://github.com/clangen/musikcube/")
> + (commit version)))
> + (file-name (git-file-name name version))
> + (sha256
> + (base32
> + "06myr83x8jvzlzchg3jsw1163n2lcsbmb176zgnx7xxa26jpdbh1"))))
Nitpick: origin could go below source, and hash in front of base32.
> + (build-system cmake-build-system)
> + (arguments
> + (list
> + #:tests? #f ; No test suite
Note that indentation is a bit off.
> + #:configure-flags
> + #~(list
> + "-DCMAKE_BUILD_TYPE=Release"
> + "-DENABLE_BUNDLED_TAGLIB=false"
> + ;; Use the "wide" ncurses headers but don't look for them in an
> + ;; ncursesw directory. For more info:
> + ;; https://github.com/clangen/musikcube/wiki/building#compiler-cannot-find-ncurseswcursesh
> + "-DNO_NCURSESW=true"
> + ;; We will strip the binaries ourselves in the 'strip' phase.
> + "-DDISABLE_STRIP=true")))
OOC, why are use using gexp since you do not ungexp later on? Wouldn't
a regular quote, or even a quasiquote suffice?
Otherwise, LGTM.
Regards,
--
Nicolas Goaziou
next prev parent reply other threads:[~2021-12-29 23:14 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-29 17:13 [bug#52875] [PATCH] gnu: Add musikcube Leo Famulari
2021-12-29 23:13 ` Nicolas Goaziou [this message]
2021-12-31 18:20 ` bug#52875: " Leo Famulari
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=878rw380nm.fsf@nicolasgoaziou.fr \
--to=mail@nicolasgoaziou.fr \
--cc=52875@debbugs.gnu.org \
--cc=leo@famulari.name \
/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).