unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: ludo@gnu.org (Ludovic Courtès)
To: Leo Famulari <leo@famulari.name>
Cc: guix-devel@gnu.org
Subject: Re: [v2 1/1] gnu: Add peg-markdown.
Date: Sun, 29 Nov 2015 11:21:33 +0100	[thread overview]
Message-ID: <878u5hp0lu.fsf@gnu.org> (raw)
In-Reply-To: <91abb64a6b8279ea62bcefff711586f790c83734.1448746196.git.leo@famulari.name> (Leo Famulari's message of "Sat, 28 Nov 2015 16:32:01 -0500")

Leo Famulari <leo@famulari.name> skribis:

> * gnu/packages/markdown.scm (peg-markdown): New variable.

[...]

> +                   ;; The Makefile offers a memory leak test using
> +                   ;; Valgrind.
> +                   (add-after 'check 'leak-check
> +                              (lambda _
> +                                (zero? (system* "make" "leak-check"))))

The opening parenthesis can be aligned below the ‘d’ of ‘add-after’.

> +                  (replace
> +                    'install
> +                    (lambda* (#:key outputs #:allow-other-keys)

Ditto, with ‘install’ moved to the previous line.

> +                      ;; The Makefile does not check if the output paths exist.
> +                      (let* ((out (assoc-ref %outputs "out"))
> +                             (bin (string-append out "/bin"))
> +                             (doc (string-append out "/share/man/man1")))
> +                        (mkdir-p bin)
> +                        ;; The top-level Makefile does not have an install
> +                        ;; target, so we have to do this manually.
> +                        (zero?
> +                          (system* "make" "-C" "peg-0.1.4"
> +                                   (string-append "PREFIX=" %output)
> +                                   "CC=gcc" "install"))
> +                        ;; The Makefile does not install the manpage.
> +                        (install-file "peg-0.1.4/peg.1" doc)
> +                        ;; The manpage applies to both peg and leg.
> +                        (symlink
> +                          (string-append doc "/peg.1")
> +                          (string-append doc "/leg.1"))
> +                        #t))))))

The return value of ‘zero?’ is ignored here.

To address this and clarify the code, what about making the
symlink-manpage thing a separate phase, added after ‘install’?

> +    (synopsis "Implementation of markdown in C, using a PEG grammar")

Capitalize “Markdown” (?); I think it’s fine to remove “using a PEG
grammar”, which is more of an implementation detail and is explained in
the description.

> +    (description "This is an implementation of John Gruber's markdown in C.  It
> +uses a parsing expression grammar (PEG) to define the syntax.  This should allow

Make sure lines are below 80 chars.

Could you send an updated patch?

Thanks,
Ludo’.

      reply	other threads:[~2015-11-29 10:21 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-11-28 21:32 [v2 0/1] Add peg-markdown with proper manpages Leo Famulari
2015-11-28 21:32 ` [v2 1/1] gnu: Add peg-markdown Leo Famulari
2015-11-29 10:21   ` Ludovic Courtès [this message]

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=878u5hp0lu.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=guix-devel@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).