unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Ricardo Wurmus <rekado@elephly.net>
To: Steve Sprang <steve.sprang@gmail.com>
Cc: guix-devel@gnu.org
Subject: Re: [PATCH] gnu: Add figlet.
Date: Sun, 16 Aug 2015 07:07:18 +0200	[thread overview]
Message-ID: <87twrzom7t.fsf@elephly.net> (raw)
In-Reply-To: <CA+xn8YAUbK_47+uOV-9_WwfodQBHWCDdf7Qv2eUD1+L4j_7QKA@mail.gmail.com>

Hi Steve,

thank you for your first Guix package!  It looks great!  I do have a
couple of cosmetic comments, though.

> From 1abd103363bb12e7b8aa5f5ad1329c94b0af48e8 Mon Sep 17 00:00:00 2001
> From: Steve Sprang <scs@stevesprang.com>
> Date: Sat, 15 Aug 2015 20:08:38 -0700
> Subject: [PATCH] gnu: Add figlet.

> * gnu/packages/figlet.scm: New file.
> * gnu-system.am (GNU_SYSTEM_MODULES): Add it.

Looks good.  I just wonder if figlet could not be added to some existing
module instead of creating a new one.  Maybe “fontutils.scm”?

> +    (version "2.2.5")
> +    (source
> +     (origin
> +       (method url-fetch)
> +       (uri (string-append
> +             "ftp://ftp.figlet.org/pub/figlet/program/unix/figlet-" version ".tar.gz"))

This line is a bit long.  How about this instead:

       (uri (string-append "ftp://ftp.figlet.org/pub/figlet/program"
                           "/unix/figlet-" version ".tar.gz"))

> +       (sha256 (base32
> +                "0za1ax15x7myjl8jz271ybly8ln9kb9zhm1gf6rdlxzhs07w925z"))))

I think it would look better like this:

       (sha256
        (base32 "0za1ax15x7myjl8jz271ybly8ln9kb9zhm1gf6rdlxzhs07w925z"))

> +    (build-system gnu-build-system)
> +    (arguments
> +     `(#:phases
> +       (alist-replace
> +        'configure
> +        (lambda* (#:key outputs #:allow-other-keys)
> +          (let ((out (assoc-ref outputs "out")))
> +            (substitute* "Makefile"
> +              (("/usr/local") out))))
> +        %standard-phases)))

I suggest using ‘(modify-phases ...)’ instead, as adding or removing
phases later on does not alter the indentation of other phases.

However, in this case ‘/usr/local’ doesn’t have to be patched away at
all.  You could just pass a make-flag to set ‘prefix’ to ‘(assoc-ref
outputs "out")’.

> +    (synopsis "Program for making large letters out of ordinary text")
> +    (description "FIGlet is a program for making large letters out of ordinary text.")

This line is too long.  You can automatically format it in Emacs with
‘M-q’.  Maybe the description could be a little longer to explain that
what figlet generates is some sort of ASCII art letters, because this
description could be misunderstood as operating on fonts.  Or maybe it’s
just me being dense ;)

> +    (home-page "http://www.figlet.org/")
> +    (license bsd-3)))

Looking at the sources it looks like not all files are under the BSD-3
license.  ‘inflate.c’, for example, is released under expat/X11;
‘getopt.c’ is public domain software — I’m not sure if this warrants
using a list for the license field.  Maybe someone else could weigh in
on this.

~~ Ricardo

  reply	other threads:[~2015-08-16  5:07 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-08-16  3:24 [PATCH] gnu: Add figlet Steve Sprang
2015-08-16  5:07 ` Ricardo Wurmus [this message]
2015-08-17 22:47   ` Steve Sprang
2015-08-18  5:48     ` Ricardo Wurmus
2015-08-19 22:43       ` Ludovic Courtès
2015-08-20  6:34         ` Ricardo Wurmus

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=87twrzom7t.fsf@elephly.net \
    --to=rekado@elephly.net \
    --cc=guix-devel@gnu.org \
    --cc=steve.sprang@gmail.com \
    /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).