From: Pierre Neidhardt <ambrevar@gmail.com>
To: Leo Famulari <leo@famulari.name>
Cc: 31114@debbugs.gnu.org
Subject: [bug#31114] [PATCH] gnu: Add fortune-mod.
Date: Tue, 10 Apr 2018 12:30:51 +0530 [thread overview]
Message-ID: <87fu43fsv0.fsf@gmail.com> (raw)
In-Reply-To: <20180409205516.GA28883@jasmine.lan>
[-- Attachment #1: Type: text/plain, Size: 1028 bytes --]
Leo Famulari <leo@famulari.name> writes:
> For an example of how to do that, look at the native-inputs field of the
> Git package definition. The Git manpages are downloaded separately for
> that package.
Thanks for the hint, it works like a charm!
(add-after 'unpack 'fix-build-env
(lambda* (#:key inputs #:allow-other-keys)
(let* ((cmake-rules (assoc-ref inputs "cmake-rules")))
(copy-file cmake-rules "fortune-mod/cmake/Shlomif_Common.cmake")
(chdir "fortune-mod"))))
One nit: I want to install the file without specifying its destination
name (re-use the source name).
~install-file~ can do that but here ~cmake-rules~ contains the checksum
prefix.
I remember seeing a procedure to trim the checksum prefix from file
names somewhere...
More generally: is there an API reference or is it just the source code?
Development documentation seems a bit scarce...
--
Pierre Neidhardt
You will gain money by a speculation or lottery.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 487 bytes --]
next prev parent reply other threads:[~2018-04-10 7:02 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-09 17:32 [bug#31114] [PATCH] gnu: Add fortune-mod Pierre Neidhardt
2018-04-09 17:39 ` Pierre Neidhardt
2018-04-09 20:51 ` Ludovic Courtès
2018-04-10 7:05 ` Pierre Neidhardt
2018-04-10 7:24 ` Pierre Neidhardt
2018-04-10 10:14 ` Ludovic Courtès
2018-04-10 16:22 ` Pierre Neidhardt
2018-04-19 9:56 ` bug#31114: " Ludovic Courtès
2018-04-19 12:34 ` [bug#31114] " Pierre Neidhardt
2018-04-23 15:12 ` Ludovic Courtès
2018-04-09 20:55 ` Leo Famulari
2018-04-10 7:00 ` Pierre Neidhardt [this message]
2018-04-18 20:42 ` Ludovic Courtès
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=87fu43fsv0.fsf@gmail.com \
--to=ambrevar@gmail.com \
--cc=31114@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).