From: Joshua G Lock <joshua.g.lock@linux.intel.com>
To: "Burton, Ross" <ross.burton@intel.com>,
Dengke Du <dengke.du@windriver.com>
Cc: OE-core <openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 2/2] perf: enable man pages for 'help' functionality
Date: Tue, 02 Aug 2016 21:06:29 +0100 [thread overview]
Message-ID: <1470168389.2984.24.camel@linux.intel.com> (raw)
In-Reply-To: <CAJTo0LaevDthmEf=w4Z0CE3C4d3G4-FUxOu8yJaFX8NjdzZDCg@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1329 bytes --]
On Tue, 2016-08-02 at 17:56 +0100, Burton, Ross wrote:
> Hi,
>
> > On 27 July 2016 at 06:02, Dengke Du <dengke.du@windriver.com> wrote:
> > > > When using 'perf help <subcommand>', it can't find 'man' command
and pages for
> > perf.
> >
> > > > The perf man pages depends on the xmlto-native and asciidoc-native,
so we just
> >
> > > > need to add the two packages to the DEPENDS variable and add
'man'to
> >
> > RDEPENDS_perf-doc.
> >
>
> > > > Whilst I like the idea of supporting more documentation, and have
long wanted to integrate doxygen/gtk-doc/etc into Yocto for building
SDKs with API documentation, I'm not sure we should be making random
packages depend on tooling to always generate documentation.
>
> > > > > > What do people think of a distro feature / global environment
variable for "recipe should build the documentation"? For perf this
would mean adding asciidoc so it can build the man pages, for GLib it
would mean depending on gtk-doc so the API docs can be generated, and
so on. But if they're not needed then they can be disabled to
improve build speeds.
>
>
I like the idea. I've had a similar one in mind for a while now as it
would be a nice feature to be able to provide the documentation for an
image as an output of the system.
Regards,
Joshua
[-- Attachment #2: Type: text/html, Size: 1741 bytes --]
next prev parent reply other threads:[~2016-08-02 20:06 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-27 5:02 [PATCH 0/2] perf: enable man pages for 'help' functionality Dengke Du
2016-07-27 5:02 ` [PATCH 1/2] Asciidoc: add it Dengke Du
2016-07-27 5:02 ` [PATCH 2/2] perf: enable man pages for 'help' functionality Dengke Du
2016-08-02 16:56 ` Burton, Ross
2016-08-02 20:06 ` Joshua G Lock [this message]
2016-07-27 18:23 ` [PATCH 0/2] " Randy MacLeod
2016-08-01 1:33 ` dengke.du
2016-08-02 17:59 ` Randy MacLeod
2016-08-04 1:35 ` dengke.du
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=1470168389.2984.24.camel@linux.intel.com \
--to=joshua.g.lock@linux.intel.com \
--cc=dengke.du@windriver.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=ross.burton@intel.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