From: Mathieu Lirzin <mthl@openmailbox.org>
To: David Thompson <dthompson2@worcester.edu>
Cc: guix-devel@gnu.org
Subject: Re: [PATCH] gnu: Add hoedown.
Date: Sun, 19 Jul 2015 19:19:03 +0200 [thread overview]
Message-ID: <87h9p06p6g.fsf@openmailbox.org> (raw)
In-Reply-To: <87zj2sb3py.fsf@izanagi.i-did-not-set--mail-host-address--so-tickle-me> (David Thompson's message of "Sun, 19 Jul 2015 10:51:21 -0400")
David Thompson <dthompson2@worcester.edu> writes:
> Here's a package recipe for a Markdown library written in C. I want to
> try to make Guile bindings for it with the FFI.
Nice idea!
> +(define-module (gnu packages markdown)
> + #:use-module (guix licenses)
> + #:use-module (guix packages)
> + #:use-module (guix download)
> + #:use-module (guix packages)
> + #:use-module (guix build-system gnu)
> + #:use-module (gnu packages python)
> + #:use-module (gnu packages web))
guix packages is added two times. Maybe "prefix:" for licences to be
safe ?
> + (substitute* '("Makefile")
> + (("/usr/local")
> + (assoc-ref outputs "out")))
No need to use a list of files here. I noticed some warnings in the
compilation process which can be fixed like this.
--8<---------------cut here---------------start------------->8---
(substitute* "Makefile"
(("-ansi") "-std=c99")
(("/usr/local") (assoc-ref outputs "out")))
--8<---------------cut here---------------end--------------->8---
> + (native-inputs
> + `(("python" ,python-2)
> + ("tidy" ,tidy)))
perl is needed in native-inputs for "test/MarkdownTest_1.0.3/MarkdownTest.pl"
Otherwise LGTM! (if i'm entitled to ;))
I will send a patch for moving the "markdown" package to this new file after
that.
--
Mathieu Lirzin
next prev parent reply other threads:[~2015-07-19 17:21 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-19 14:51 [PATCH] gnu: Add hoedown David Thompson
2015-07-19 17:19 ` Mathieu Lirzin [this message]
2015-07-20 0:01 ` Thompson, David
2015-07-21 18:53 ` Mark H Weaver
2015-07-21 19:04 ` Thompson, David
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87h9p06p6g.fsf@openmailbox.org \
--to=mthl@openmailbox.org \
--cc=dthompson2@worcester.edu \
--cc=guix-devel@gnu.org \
/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 external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.