From: Brian Inglis <Brian.Inglis@SystematicSw.ab.ca>
To: cygwin@cygwin.com
Subject: Re: No gawk-doc package, gawk source autoconf fails
Date: Thu, 10 Nov 2016 21:29:00 -0000 [thread overview]
Message-ID: <6c34e922-aa0d-acab-873b-70464481df39@SystematicSw.ab.ca> (raw)
In-Reply-To: <20161110092428.GD6075@calimero.vinschen.de>
On 2016-11-10 02:24, Corinna Vinschen wrote:
> On Nov 9 18:29, Yaakov Selkowitz wrote:
>> On 2016-11-09 18:02, Brian Inglis wrote:
>>> Looked for gawk doc in /usr/share/doc/gawk*/ - no HTML, PDF etc.
>>> Checked for gawk doc as a package - no gawk-doc or anything like
>>> it.
>>> Downloaded gawk package source and tried to configure enough to
>>> build doc.
>>> Seems to be problem with autoconf autopoint gettext package
>>> version - something run by autoreconf seems to be detecting
>>> gettext 0.19.8-1 as 0.19.8.1 instead of 0.19.8 which causes
>>> autopoint to fail:
>> This is already fixed in cygport git master.
Thanks for that - fixing a gettext nano-release with an extra .#
autopoint dislikes.
> Do I have to create a fixed gawk package at one point? Perhaps
> after the next cygport release?
It would be a kindness if the maintainer built the docs and
provided a gawk-doc package like other distros with the next
gawk release.
It would be nice if it included the examples, manuals, and
cards in man, info, html, ps, and pdf formats, unlike most
distros.
Can never have too many doc formats, depending on what you're
doing, what you're looking for, and what you have available.
Regular man and info are good for grepping, html single page
is good for phones and ereaders, multi page and PDF are better
on tablets and desktops.
--
Take care. Thanks, Brian Inglis, Calgary, Alberta, Canada
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
prev parent reply other threads:[~2016-11-10 19:58 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-10 0:02 Brian Inglis
2016-11-10 0:29 ` Yaakov Selkowitz
2016-11-10 9:24 ` Corinna Vinschen
2016-11-10 21:29 ` Brian Inglis [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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=6c34e922-aa0d-acab-873b-70464481df39@SystematicSw.ab.ca \
--to=brian.inglis@systematicsw.ab.ca \
--cc=cygwin@cygwin.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.
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).