From: Alex Kost <alezost@gmail.com>
To: Federico Beffa <beffa@ieee.org>
Cc: Guix-devel <guix-devel@gnu.org>
Subject: Re: [PATCH 6/6] gnu: Add emacs-slime.
Date: Sat, 09 Jan 2016 18:27:23 +0300 [thread overview]
Message-ID: <874mempyck.fsf@gmail.com> (raw)
In-Reply-To: <CAKrPhPPknwsBPVsPw+M6wNouw-JdSrohRX8fMFmrAK5q=3i8+g@mail.gmail.com> (Federico Beffa's message of "Sat, 9 Jan 2016 11:30:16 +0100")
Federico Beffa (2016-01-09 13:30 +0300) wrote:
> On Tue, Jan 5, 2016 at 11:17 PM, Ludovic Courtès <ludo@gnu.org> wrote:
>> Federico Beffa <beffa@ieee.org> skribis:
>>> + (add-before 'install 'install-doc
>>> + (lambda* (#:key outputs #:allow-other-keys)
>>> + (let* ((out (assoc-ref outputs "out"))
>>> + (info-dir (string-append out "/share/info"))
>>> + (doc-dir (string-append out "/share/doc/"
>>> + ,name "-" ,version))
>>> + (doc-files '("doc/slime.pdf" "doc/slime-refcard.pdf"
>>> + "README.md" "NEWS" "PROBLEMS"
>>> + "CONTRIBUTING.md")))
>>> + (with-directory-excursion "doc"
>>> + (substitute* "Makefile"
>>> + (("infodir=/usr/local/info")
>>> + (string-append "infodir=" info-dir)))
>>> + (system* "make" "all")
>>> + (install-file "slime.info" info-dir)
>>> + (copy-recursively "html" (string-append doc-dir "/html")))
>>> + (for-each (lambda (f)
>>> + (install-file f doc-dir)
>>> + (delete-file f))
>>> + doc-files)
>>> + (delete-file-recursively "doc")
>>
>> Can we build and install only Info files? This is what we usually do
>> for packages that have Texinfo manuals. Incidentally, it allows us to
>> get rid of the TeX Live dependency.
>
> I'm OK to remove slime.pdf, but the slime-refcard.pdf is quite useful.
> (See mit-scheme thread for my opinion on TeXLive.)
I think texlive is not needed for "slime-refcard.pdf" as this pdf is
available in the source: <https://github.com/slime/slime/tree/master/doc>.
--
Alex
next prev parent reply other threads:[~2016-01-09 15:27 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-30 17:33 [PATCH 6/6] gnu: Add emacs-slime Federico Beffa
2015-12-31 0:55 ` Ben Woodcroft
2015-12-31 9:12 ` Federico Beffa
2016-01-05 22:17 ` Ludovic Courtès
2016-01-09 10:30 ` Federico Beffa
2016-01-09 15:27 ` Alex Kost [this message]
2016-01-09 18:45 ` Ludovic Courtès
2015-12-31 9:52 ` Ricardo Wurmus
2015-12-31 23:52 ` Alex Kost
2016-01-01 8:25 ` Ricardo Wurmus
2016-01-01 8:35 ` Ben Woodcroft
2016-01-01 15:04 ` Ricardo Wurmus
2016-01-05 14:25 ` [PATCH] import: Move beautify description from cran to utils. (was Re: [PATCH 6/6] gnu: Add emacs-slime.) Ben Woodcroft
2016-01-10 21:17 ` Ludovic Courtès
2016-01-14 9:49 ` Ben Woodcroft
2016-01-14 10:31 ` Ricardo Wurmus
2016-01-14 10:53 ` Ben Woodcroft
2016-01-14 11:30 ` Ricardo Wurmus
2016-01-14 12:15 ` Ben Woodcroft
2016-01-17 1:00 ` [PATCH] import: Move beautify description from cran to utils Ben Woodcroft
2016-01-18 9:45 ` Ludovic Courtès
2016-01-20 22:13 ` Ben Woodcroft
2016-01-21 8:51 ` Ludovic Courtès
2015-12-31 10:17 ` [PATCH 6/6] gnu: Add emacs-slime Alex Kost
2015-12-31 10:32 ` Federico Beffa
2015-12-31 20:40 ` Alex Kost
2015-12-31 10:33 ` Alex Kost
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=874mempyck.fsf@gmail.com \
--to=alezost@gmail.com \
--cc=beffa@ieee.org \
--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 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).