From: Arnout Vandecappelle <arnout@mind.be>
To: buildroot@busybox.net
Subject: [Buildroot] [git commit] kmod: disable manpages for host-kmod
Date: Wed, 04 Sep 2013 22:27:45 +0200 [thread overview]
Message-ID: <522797C1.7040002@mind.be> (raw)
In-Reply-To: <87mwns4a78.fsf@dell.be.48ers.dk>
On 09/04/13 22:13, Peter Korsgaard wrote:
>>>>>> "Thomas" == Thomas Petazzoni <thomas.petazzoni@free-electrons.com> writes:
>
> Thomas> Dear J?r?me Pouiller,
> Thomas> On Wed, 04 Sep 2013 17:50:47 +0200, J?r?me Pouiller wrote:
>
> >> > ifneq ($(BR2_HAVE_DOCUMENTATION),y)
> >> > KMOD_CONF_OPT += --disable-manpages
> >> > endif
> >> What happens when BR2_HAVE_DOCUMENTATION is enabled? I think same
> >> problem happens.
> >>
> >> We should add a dependency to host-libxslt and I think we can pass
> >> variable XSLTPROC= to ./configure to use a specific location of
> >> xsltproc.
>
> Thomas> Yes, we normally should. But nobody seems to be testing or using
> Thomas> BR2_HAVE_DOCUMENTATION. I would personally be in favor of just getting
> Thomas> rid of BR2_HAVE_DOCUMENTATION. Who needs the documentation to be
> Thomas> installed on the target?
>
> I'm also starting to think so. With Buildroot focused on cross
> compilation (and the development on target stuff gone), I don't see much
> use for documentation on the target either.
Well, if you have a less space-constrained system it's kind of
convenient to be able to pull up a man page for some tool that you're
less familiar with and that is not installed on your host (not that I can
think of an example :-). However, in its current incarnation, including
documentation adds a huge amount of bloat. Taking one random output I
find 105MB in the target dir and 40MB of various bits of documentation in
the staging dir.
Bottom line: yes, BR2_HAVE_DOCUMENTATION can be killed.
Regards,
Arnout
--
Arnout Vandecappelle arnout at mind be
Senior Embedded Software Architect +32-16-286500
Essensium/Mind http://www.mind.be
G.Geenslaan 9, 3001 Leuven, Belgium BE 872 984 063 RPR Leuven
LinkedIn profile: http://www.linkedin.com/in/arnoutvandecappelle
GPG fingerprint: 7CB5 E4CC 6C2E EFD4 6E3D A754 F963 ECAB 2450 2F1F
prev parent reply other threads:[~2013-09-04 20:27 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-04 10:36 [Buildroot] [git commit] kmod: disable manpages for host-kmod Peter Korsgaard
2013-09-04 15:50 ` Jérôme Pouiller
2013-09-04 16:19 ` Thomas Petazzoni
2013-09-04 20:13 ` Peter Korsgaard
2013-09-04 20:27 ` Arnout Vandecappelle [this message]
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=522797C1.7040002@mind.be \
--to=arnout@mind.be \
--cc=buildroot@busybox.net \
/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.