From: Alexander Kanavin <alexander.kanavin@linux.intel.com>
To: openembedded-core@lists.openembedded.org, "Ohly,
Patrick" <patrick.ohly@intel.com>
Subject: Re: [PATCH] manpages.bbclass: avoid QA warning when "manpages" feature not supported
Date: Mon, 15 May 2017 14:47:40 +0300 [thread overview]
Message-ID: <237a1d6e-7c01-2488-c6a2-e5d0c95aff53@linux.intel.com> (raw)
In-Reply-To: <9f9ebf2e1ba6eda48fb5e3f20d4ca5bbabe3dad4.1494837087.git-series.patrick.ohly@intel.com>
On 05/15/2017 11:32 AM, Patrick Ohly wrote:
> Activating API documentation with:
> INHERIT += "manpages"
> DISTRO_FEATURES_append = " api-documentation"
You do not need to add the first line at all, why are you doing it?
manpages is inherited on a per-recipe basis when the recipe itself
supports the manpages PACKAGECONFIG. This patch is unnecessary.
Alex
next prev parent reply other threads:[~2017-05-15 11:49 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-15 8:32 [PATCH] manpages.bbclass: avoid QA warning when "manpages" feature not supported Patrick Ohly
2017-05-15 11:47 ` Alexander Kanavin [this message]
2017-05-15 12:24 ` Patrick Ohly
2017-05-15 13:06 ` Burton, Ross
2017-05-24 20:54 ` Jose Lamego
2017-05-24 20:57 ` Jose Lamego
2017-05-25 8:06 ` Alexander Kanavin
2017-05-25 14:21 ` Jose Lamego
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=237a1d6e-7c01-2488-c6a2-e5d0c95aff53@linux.intel.com \
--to=alexander.kanavin@linux.intel.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=patrick.ohly@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