From: Rutger Helling <rhelling@mykolab.com>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: guix-devel@gnu.org
Subject: Re: 02/02: gnu: wine64-staging: Copy missing man file.
Date: Wed, 3 Jan 2018 11:13:52 +0100 [thread overview]
Message-ID: <20180103111352.0e6a25fa@mykolab.com> (raw)
In-Reply-To: <87vagjx5hv.fsf@gnu.org>
[-- Attachment #1: Type: text/plain, Size: 1252 bytes --]
That code was indeed a bit wacky, I fixed it up.
On Tue, 02 Jan 2018 23:25:48 +0100
ludo@gnu.org (Ludovic Courtès) wrote:
> Hi,
>
> This is your friendly nitpicking bot! ;-)
>
> rhelling@mykolab.com (Rutger Helling) skribis:
>
> > "/bin/wine-preloader")
> > (string-append (assoc-ref %outputs "out")
> > "/bin/wine-preloader"))
> > + ;; Copy the missing man file for the wine binary from
> > wine-staging.
> > + (system (string-append "gunzip < " (string-append
> > (assoc-ref
> > + %build-inputs "wine-staging")
> > + "/share/man/man1/wine.1.gz")
> > "> "
> > + (string-append (assoc-ref
> > %outputs "out")
> > + "/share/man/man1/wine.1")))
> > #t))
>
> The indentation of the nested ‘string-append’ calls is misleading here
> (and the nested calls are unnecessary because ‘string-append’ is
> n-ary.)
>
> Also, I think it’s OK to leave the file compressed (we have a man page
> compression phase anyway.)
>
> Thanks!
>
> Ludo’.
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
prev parent reply other threads:[~2018-01-03 10:14 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20180102104042.1024.9064@vcs0.savannah.gnu.org>
[not found] ` <20180102104045.DDA98206A2@vcs0.savannah.gnu.org>
2018-01-02 22:25 ` 02/02: gnu: wine64-staging: Copy missing man file Ludovic Courtès
2018-01-03 10:13 ` Rutger Helling [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=20180103111352.0e6a25fa@mykolab.com \
--to=rhelling@mykolab.com \
--cc=guix-devel@gnu.org \
--cc=ludo@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 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).