From: Corinna Vinschen <corinna-cygwin@cygwin.com>
To: cygwin-patches@cygwin.com
Subject: Re: [PATCH 5/8] winsup/doc: Convert utils.xml to using refentry
Date: Tue, 16 Jun 2015 19:17:00 -0000 [thread overview]
Message-ID: <20150616191712.GH31537@calimero.vinschen.de> (raw)
In-Reply-To: <55806FF7.3010600@dronecode.org.uk>
[-- Attachment #1: Type: text/plain, Size: 1989 bytes --]
On Jun 16 19:50, Jon TURNEY wrote:
> On 16/06/2015 18:49, Corinna Vinschen wrote:
> >>Note that the next time you build documentation for the website, you might
> >>need to take some special steps to add new .html files.
> >
> >-v, please?
>
> Sorry, I wasn't being intentionally vague, but I don't know precisely how
> you push documentation updates.
>
> I guess you will need to do a 'cvs add *.html'
Oh, I see. I didn't realize from the start that utils.xml is also split
into multiple html files now.
> >>and next time you build a package you might need to take some special steps
> >>to exclude /usr/share/man/
> >
> >What special steps? I assume a `make install' will install the
> >additional man pages now. Wouldn't it make sense to install them as
> >part of the Cygwin package then, rather than as part of cygwin-doc?
>
> Ultimately, I think it would be a good idea if cygwin-doc was generated by
> the same process which builds the cygwin(|-devel|-debuginfo) packages.
Yes, that sounds right to me...
> But we are some way from there yet.
...and I'm open to patches to make it reality :)
> My thought was that the simplest way to do the transition is to exclude all
> the files currently owned by cygwin-doc until then, but maybe you have a
> different idea.
Hmm, no. The cygwin package comes with the PDF and HTML files under
/usr/share/doc/cygwin-${PV}, the cygwin-devel package with the files
/usr/share/man/man3/regex.3.gz
/usr/share/man/man7/regex.7.gz
(and an undesired usr/share/man/man3/2.0.3.gz, which I only now see.
Oh well)
In theory these man pages as well as the other doc files would be
ideally bundled with the cygwin-doc package at one point.
For the time being, I look into excluding the utils man pages in the
cygwin package.
Corinna
--
Corinna Vinschen Please, send mails regarding Cygwin to
Cygwin Maintainer cygwin AT cygwin DOT com
Red Hat
[-- Attachment #2: Type: application/pgp-signature, Size: 819 bytes --]
next prev parent reply other threads:[~2015-06-16 19:17 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-15 12:36 [PATCH 0/8] Generate utilities manpages Jon TURNEY
2015-06-15 12:37 ` [PATCH 4/8] winsup/doc: Use fo.xsl to customize PDF generation from DocBook XML Jon TURNEY
2015-06-15 17:05 ` Corinna Vinschen
2015-06-15 12:37 ` [PATCH 8/8] winsup/doc: Fix an issue with parallel make Jon TURNEY
2015-06-15 17:16 ` Corinna Vinschen
2015-06-15 12:37 ` [PATCH 1/8] winsup/doc: Remove tarball target from .PHONY Jon TURNEY
2015-06-15 16:52 ` Corinna Vinschen
2015-06-15 12:37 ` [PATCH 2/8] winsup/doc: Fix xidepend to handle relative pathnames Jon TURNEY
2015-06-15 17:02 ` Corinna Vinschen
2015-06-15 12:37 ` [PATCH 7/8] winsup/doc: Make and install manpages for utils Jon TURNEY
2015-06-15 18:12 ` Corinna Vinschen
2015-06-15 12:37 ` [PATCH 6/8] winsup/doc: Make it easier to extend xidepend to more targets Jon TURNEY
2015-06-15 17:15 ` Corinna Vinschen
2015-06-15 12:37 ` [PATCH 5/8] winsup/doc: Convert utils.xml to using refentry Jon TURNEY
2015-06-15 17:11 ` Corinna Vinschen
2015-06-16 9:28 ` Jon TURNEY
2015-06-16 9:45 ` Corinna Vinschen
2015-06-16 11:09 ` Jon TURNEY
2015-06-16 12:49 ` Corinna Vinschen
2015-06-16 17:33 ` Jon TURNEY
2015-06-16 17:49 ` Corinna Vinschen
2015-06-16 18:50 ` Jon TURNEY
2015-06-16 19:17 ` Corinna Vinschen [this message]
2015-06-15 12:37 ` [PATCH 3/8] winsup/doc: Some preparatory XML fixes Jon TURNEY
2015-06-15 17:04 ` Corinna Vinschen
2015-06-16 9:22 ` Jon TURNEY
2015-06-16 9:35 ` Corinna Vinschen
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=20150616191712.GH31537@calimero.vinschen.de \
--to=corinna-cygwin@cygwin.com \
--cc=cygwin-patches@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).