From: Ken Brown <kbrown@cornell.edu>
To: cygwin-announce@cygwin.com
Subject: texinfo 6.5-1
Date: Wed, 13 Sep 2017 14:08:00 -0000 [thread overview]
Message-ID: <201709131223.v8DCN5uK031515@authusersmtp.mail.cornell.edu> (raw)
The following packages have been uploaded to the Cygwin distribution:
* texinfo-6.5-1
* texinfo-tex-6.5-1
* info-6.5-1
Texinfo is a documentation system that uses a single source file to
produce output in a number of formats, both online and printed (dvi,
html, info, pdf, xml, etc.).
This is an update to the latest upstream release. It is primarily a
bugfix release. See the announcement at
http://lists.gnu.org/archive/html/bug-texinfo/2017-09/msg00013.html
for more details.
Cygwin packaging
================
The info package contains the standalone info viewer as well as the
install-info program. The texinfo package contains everything else
except support for the printable output formats (such as pdf). The
texinfo-tex package supplies the latter. In particular,
/usr/bin/makeinfo is in the texinfo package, but the command 'makeinfo
--pdf' won't work unless you install texinfo-tex.
Ken Brown
Cygwin's texinfo maintainer
reply other threads:[~2017-09-13 14:08 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=201709131223.v8DCN5uK031515@authusersmtp.mail.cornell.edu \
--to=kbrown@cornell.edu \
--cc=cygwin-announce@cygwin.com \
--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).