From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 4 of 7] packages: remove support for documentation on target
Date: Wed, 5 Feb 2014 14:16:26 +0100 [thread overview]
Message-ID: <20140205141626.654ac08a@skate> (raw)
In-Reply-To: <CAAXf6LV0DwSccqT8Ur7p=NXn70FFka212O4t9pBbsS6t1VmuOQ@mail.gmail.com>
Dear Thomas De Schampheleire,
On Wed, 5 Feb 2014 14:10:09 +0100, Thomas De Schampheleire wrote:
> > So the DISABLE_DOCUMENTATION variable now always has the same value,
> > and is only used in pkg-autotools.mk in one place. So I believe it
> > makes sense to remove this variable altogether, and simply pass all the
> > appropriate --<something> options directly in the <pkg>_CONFIGURE_CMDS
> > of pkg-autotools.mk.
>
> OK.
> By the way, I added on my own todo list that we should try to expand
> the automatically passed options, for example:
> --disable-manpages --disable-man-pages --disable-manuals etc. as some
> of them are used in several packages...
I have a mixed feeling about this. The problem is that those options
are not standard, so by far not all configure scripts understand them.
Which means that when a given configure script is called, you often
have a warning:
WARNING: options --disable-foo --enable-bar unsupported
If you have gazillions of options that are unsupported, then you may
very well miss an option passed by your .mk file on which you made a
typo, for example.
So having a long list of options to disable documentation is not
something that I personally like that much, but I believe Arnout does
not share the same opinion :)
> > Then merge this KMOD_CONF_OPT += line with the existing KMOD_CONF_OPT
> > line above.
>
> I did not do that because the --disable-static --enable-shared setting
> is accompanied with a comment:
> # static linking not supported, see
> # https://git.kernel.org/cgit/utils/kernel/kmod/kmod.git/commit/?id=b7016153ec8
> KMOD_CONF_OPT = --disable-static --enable-shared
>
> and I felt that adding --disable-manpages here would be confusing.
> With this extra info, what is your position?
Ah, ok. In that case then it would be more natural maybe to have first
the mandatory normal options, and then this special shared/static
thing. Like:
KMOD_CONF_OPT = --disable-manpages
# blabla static blabla shared
KMOD_CONF_OPT += --disable-static --enable-shared
All these comments are cosmetic comment, so I'm in favor of merging
your patch set as is, and do followup improvements as needed.
Best regards,
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2014-02-05 13:16 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-05 10:50 [Buildroot] [PATCH 0 of 7] Remove remaining deprecated packages for 2014.02 Thomas De Schampheleire
2014-02-05 10:50 ` [Buildroot] [PATCH 1 of 7] xstroke: remove deprecated package Thomas De Schampheleire
2014-02-05 10:50 ` [Buildroot] [PATCH 2 of 7] autoconf: remove deprecated target package Thomas De Schampheleire
2014-02-05 10:50 ` [Buildroot] [PATCH 3 of 7] automake: " Thomas De Schampheleire
2014-02-05 10:50 ` [Buildroot] [PATCH 4 of 7] packages: remove support for documentation on target Thomas De Schampheleire
2014-02-05 12:49 ` Thomas Petazzoni
2014-02-05 13:10 ` Thomas De Schampheleire
2014-02-05 13:16 ` Thomas Petazzoni [this message]
2014-02-05 13:28 ` Thomas De Schampheleire
2014-02-05 13:34 ` Thomas Petazzoni
2014-02-05 21:21 ` Arnout Vandecappelle
2014-02-06 8:37 ` Thomas Petazzoni
2014-02-06 10:26 ` Arnout Vandecappelle
2014-02-06 11:34 ` Thomas De Schampheleire
2014-02-06 11:40 ` Thomas Petazzoni
2014-02-06 12:15 ` Thomas De Schampheleire
2014-02-06 13:33 ` Arnout Vandecappelle
2014-02-06 22:19 ` Peter Korsgaard
2014-02-05 10:50 ` [Buildroot] [PATCH 5 of 7] ccache: remove deprecated target package Thomas De Schampheleire
2014-02-05 10:50 ` [Buildroot] [PATCH 6 of 7] gdb: remove deprecated versions 7.2.x and 7.3.x Thomas De Schampheleire
2014-02-05 10:50 ` [Buildroot] [PATCH 7 of 7] kernel-headers: remove deprecated versions 3.1, 3.3, 3.5 Thomas De Schampheleire
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=20140205141626.654ac08a@skate \
--to=thomas.petazzoni@free-electrons.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox