From: "Ludovic Courtès" <ludo@gnu.org>
To: Leo Prikler <leo.prikler@student.tugraz.at>
Cc: 38480@debbugs.gnu.org, Brett Gilio <brettg@posteo.net>
Subject: [bug#38480] [PATCH] gnu: Add lolcat
Date: Sun, 15 Dec 2019 00:28:34 +0100 [thread overview]
Message-ID: <87k16ywkpp.fsf@gnu.org> (raw)
In-Reply-To: <fa8f7a346d9f190892f49e1538ed909d184c1412.camel@student.tugraz.at> (Leo Prikler's message of "Thu, 05 Dec 2019 18:41:40 +0100")
Hello!
Leo Prikler <leo.prikler@student.tugraz.at> skribis:
> From: Leo Prikler <leo.prikler@student.tugraz.at>
> Date: Wed, 4 Dec 2019 02:46:44 +0100
> Subject: [PATCH] gnu: Add lolcat
>
> * gnu/packages/games.scm (lolcat): New package.
[...]
> + (replace 'install
> + (lambda* (#:key outputs #:allow-other-keys)
> + (let ((dest (map (lambda (path) (string-append path "/bin"))
> + (list (assoc-ref outputs "out")
> + (assoc-ref outputs "censor")))))
> + (for-each mkdir-p dest)
> + (install-file "lolcat" (car dest))
> + (install-file "censor" (cadr dest))
> + #t))))))
> + (outputs (list "out" "censor"))
Can’t we keep them both in the same output? Separate outputs are
normally only used when it helps save space, but I don’t think that’s a
concern here. :-)
> + (home-page "https://github.com/jaseg/lolcat")
> + (synopsis "Rainbow coloring effect for text console display")
> + (description "Lolcat concatenates files and streams like regular cat,
^ ^
Maybe @command{cat} and @command{lolcat}.
Could you send an updated patch?
Thanks,
Ludo’.
next prev parent reply other threads:[~2019-12-14 23:29 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-04 1:46 [bug#38480] [PATCH] gnu: Add lolcat Leo Prikler
2019-12-04 3:00 ` Brett Gilio
2019-12-05 17:41 ` Leo Prikler
2019-12-14 23:28 ` Ludovic Courtès [this message]
2019-12-15 0:10 ` Leo Prikler
2019-12-15 20:59 ` bug#38480: " 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=87k16ywkpp.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=38480@debbugs.gnu.org \
--cc=brettg@posteo.net \
--cc=leo.prikler@student.tugraz.at \
/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).