From: Per Bothner <per@bothner.com>
To: David Pirotte <david@altosw.be>
Cc: kawa@sourceware.org
Subject: Re: please checkout Kawa from gitlab.com
Date: Wed, 23 Nov 2016 07:42:00 -0000 [thread overview]
Message-ID: <6c5af6ca-b066-0d99-f888-26d5934c8c22@bothner.com> (raw)
In-Reply-To: <20161122201232.31576a93@capac>
On 11/22/2016 02:12 PM, David Pirotte wrote:
>
> if I make install twice (I did it by mistake), it fails the second time
> with this message
>
> cd /opt/bin && \
> ln -s /opt/share/kawa/bin/kawa kawa
> ln: failed to create symbolic link 'kawa': File exists
Thanks - I checked in a fix for this.
> I like to install html doc locally, it fails
>
> ./configure --prefix=/opt
> make. make install, make install-html
>
> -> it installs kawa doc in my home drectory instead of /opt/share/doc/kawa
> as expected
>
> it fails see below
This one is harder. The 'install-html' rule is rather bit-rotted; it should
probably be removed. Not sure what to replace it with, if anything.
As far as I know, there is no GNU standard for installing html files.
I would like change this; see http://per.bothner.com/blog/2016/texinfo-roadmap/
(which is still a rough draft).
There are two (or three) mechanisms for making html documentation
(all these assuming you're in the doc directory):
(1) 'make kawa-html', which uses 'makeinfo --html'.
(2) A more convoluted path, which uses 'makeinfo --docbook', and then
uses the DocBook style sheets to create html or epub.
The are two sub-variants:
(2a) 'make web/index.html' creates a web-site with a navigation bar and
my own styling. This is the source of the Kawa website.
(2b) 'make kawa-manual.epub' makes a EPUB electronic book.
The file kawa-manual.epub is included with the Kawa binary distribution, and
it is used by the kawa --browse-manual command. See:
https://www.gnu.org/software/kawa/Binary-distribution.html (final subsection)
https://www.gnu.org/software/kawa/Options.html#browse-manual-option
I have mostly been focusing on (2a) and (2b), rather than (1).
The preferred way to "install the documentation" is (2b).
I'd be curious to hear if others can manage to build kawa-manual.epub.
If you want to try, you meed the DocBook XSL stylesheets, and to
override the DOCBOOK_XSL_DIR variable in doc/Makefile (or create
the symlink as described in the Makefile).
--
--Per Bothner
per@bothner.com http://per.bothner.com/
next prev parent reply other threads:[~2016-11-23 7:42 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-13 0:59 proposal: move Kawa from Subversion to git on gitlab.com Per Bothner
2016-11-13 4:42 ` Jamison Hope
2016-11-13 5:06 ` Per Bothner
2016-11-16 0:53 ` invoke branch (was: proposal: move Kawa from Subversion to git on gitlab.com) Per Bothner
2016-11-13 17:51 ` proposal: move Kawa from Subversion to git on gitlab.com David Pirotte
2016-11-13 22:55 ` Charlie Turner
2016-11-13 23:37 ` Per Bothner
2016-11-22 16:57 ` please checkout Kawa from gitlab.com Per Bothner
2016-11-22 22:12 ` David Pirotte
2016-11-23 7:42 ` Per Bothner [this message]
2016-11-23 13:17 ` make kawa-manual.epub (Re: please checkout Kawa from gitlab.com) Sudarshan S Chawathe
2016-11-23 18:05 ` Per Bothner
2016-11-27 6:07 ` Per Bothner
2016-11-25 1:33 ` please checkout Kawa from gitlab.com Kumar Appaiah
2016-11-25 5:33 ` Per Bothner
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=6c5af6ca-b066-0d99-f888-26d5934c8c22@bothner.com \
--to=per@bothner.com \
--cc=david@altosw.be \
--cc=kawa@sourceware.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.
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).