From: Mark Hatle <mark.hatle@windriver.com>
To: <openembedded-devel@lists.openembedded.org>
Subject: Re: [meta-oe][PATCH 5/5] udisks: disable manpage building
Date: Fri, 6 Jan 2012 15:13:33 -0600 [thread overview]
Message-ID: <4F0763FD.9000801@windriver.com> (raw)
In-Reply-To: <CAP9ODKqpDS=sJQ-uuP5+E6QOMU7eQheWXqk+TSA4fkpwha6LVw@mail.gmail.com>
On 1/6/12 2:10 PM, Otavio Salvador wrote:
> On Fri, Jan 6, 2012 at 17:57, Phil Blundell<philb@gnu.org> wrote:
>
>> On Fri, 2012-01-06 at 18:59 +0000, Otavio Salvador wrote:
>>> +EXTRA_OECONF = "--disable-man-pages"
>>
>> why is this desirable?
>>
>
> Because it was breaking builds for me.
>
In what way? Most of the problems I've observed in the past have been docbook
related, but I think those have been resolved within OE-Core.
Man pages are very desirable for a class of systems, so I'm hesitant to simply
remove them w/o a reason or replacement (i.e. a static page)
--Mark
next prev parent reply other threads:[~2012-01-06 21:21 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-06 18:59 [meta-oe][PATCH 0/5] Pending patches from O.S. Systems tree Otavio Salvador
2012-01-06 18:59 ` [meta-oe][PATCH 1/5] xserver-nodm-init: move systemd service to xserver-nodm-init-systemd Otavio Salvador
2012-01-06 18:59 ` [meta-oe][PATCH 2/5] meta-efl: elsa: rconflicts/rreplaces xserver-nodm-init-systemd Otavio Salvador
2012-01-06 18:59 ` [meta-oe][PATCH 3/5] task-x11: use xserver-nodm-init-systemd Otavio Salvador
2012-01-06 18:59 ` [meta-oe][PATCH 4/5] busybox: add systemd support for syslog service Otavio Salvador
2012-01-06 18:59 ` [meta-oe][PATCH 5/5] udisks: disable manpage building Otavio Salvador
2012-01-06 19:57 ` Phil Blundell
2012-01-06 20:10 ` Otavio Salvador
2012-01-06 21:13 ` Mark Hatle [this message]
2012-01-06 21:49 ` Otavio Salvador
2012-01-06 22:21 ` Otavio Salvador
2012-01-09 16:02 ` Mark Hatle
2012-01-09 17:19 ` Otavio Salvador
2012-01-22 0:16 ` Khem Raj
2012-01-09 17:31 ` Martin Jansa
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=4F0763FD.9000801@windriver.com \
--to=mark.hatle@windriver.com \
--cc=openembedded-devel@lists.openembedded.org \
/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.