From: Josh Durgin <jdurgin@redhat.com>
To: Gregory Farnum <greg@gregs42.com>, David Zafman <dzafman@redhat.com>
Cc: Sage Weil <sweil@redhat.com>, Ken Dreyer <kdreyer@redhat.com>,
"ceph-devel@vger.kernel.org" <ceph-devel@vger.kernel.org>
Subject: Re: regenerating man pages
Date: Tue, 17 Mar 2015 12:41:34 -0700 [thread overview]
Message-ID: <5508836E.10307@redhat.com> (raw)
In-Reply-To: <CAC6JEv8Gogaspvva0MygWZ5AzwXTqaNRMbfo65XtsmcYiZYagw@mail.gmail.com>
On 03/17/2015 12:32 PM, Gregory Farnum wrote:
> Yeah. If this has gotten easier it's fine, but asphyxiate required a
> *lot* of tooling that I'd rather we not require as developer build
> deps. I'd imagine we can just produce them as part of the Jenkins
> build procedure or something?
None of that is needed for man pages or developer builds. asphyxiate is
just for getting doxygen into the docs. The man pages are generated with
plain sphinx, and do not need to be part of developer builds. Only
package builds need to generate them.
Josh
> On Tue, Mar 17, 2015 at 12:27 PM, David Zafman <dzafman@redhat.com> wrote:
>>
>> I found that I could not build the docs on Ubuntu 14.10 with the proper
>> packages installed. Kefu is looking into Asphyxiate which is very
>> tempermental. I installed an Ubuntu 11.10 in order to generate docs.
>>
>> David
>>
>>
>> On 3/17/15 10:11 AM, Sage Weil wrote:
>>>
>>> On Tue, 17 Mar 2015, Josh Durgin wrote:
>>>>
>>>> On 03/17/2015 09:40 AM, Ken Dreyer wrote:
>>>>>
>>>>> I had a question about the way that we're handling man pages.
>>>>>
>>>>> In 356a749f63181d401d16371446bb8dc4f196c2a6 , "rbd: regenerate rbd(8)
>>>>> man page", it looks like man/rbd.8 was regenerated from
>>>>> doc/man/8/rbd.rst
>>>>>
>>>>> It seems like it would be more efficient to avoid storing man pages in
>>>>> Git and generate them dynamically at build time instead?
>>>>
>>>> Yes, that'd be great!
>>>>
>>>>> https://github.com/ceph/ceph/blob/master/admin/manpage-howto.txt
>>>>>
>>>>> "admin/build-doc" does a lot of things (including man page generation).
>>>>> Could we simply run the "sphinx-build -b man" part at build time as a
>>>>> part of "make"?
>>>>
>>>> I don't see a reason not to. It's just a matter of making it work on all
>>>> the platforms we're building packages for. That might be annoying for
>>>> the entirety of build-doc, but for just building man pages it should
>>>> be simple.
>>>
>>> I think the original reason we didn't was just because there are a lot of
>>> dependencies for building the docs, so this inflates Build-Depends. That
>>> doesn't particularly bother me, though, if the deps do in fact exist.
>>>
>>> sage
>>> --
>>> To unsubscribe from this list: send the line "unsubscribe ceph-devel" in
>>> the body of a message to majordomo@vger.kernel.org
>>> More majordomo info at http://vger.kernel.org/majordomo-info.html
>>
>>
>> --
>> To unsubscribe from this list: send the line "unsubscribe ceph-devel" in
>> the body of a message to majordomo@vger.kernel.org
>> More majordomo info at http://vger.kernel.org/majordomo-info.html
> --
> To unsubscribe from this list: send the line "unsubscribe ceph-devel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
next prev parent reply other threads:[~2015-03-17 19:41 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-17 16:40 regenerating man pages Ken Dreyer
2015-03-17 16:49 ` Josh Durgin
2015-03-17 17:11 ` Sage Weil
2015-03-17 19:27 ` David Zafman
2015-03-17 19:32 ` Gregory Farnum
2015-03-17 19:41 ` Josh Durgin [this message]
2015-03-17 19:44 ` Sage Weil
-- strict thread matches above, loose matches on Subject: below --
2015-03-18 6:25 kefu chai
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=5508836E.10307@redhat.com \
--to=jdurgin@redhat.com \
--cc=ceph-devel@vger.kernel.org \
--cc=dzafman@redhat.com \
--cc=greg@gregs42.com \
--cc=kdreyer@redhat.com \
--cc=sweil@redhat.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.