From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCHv3] gdb: prevent building the documentation
Date: Wed, 9 Sep 2015 16:29:00 +0200 [thread overview]
Message-ID: <20150909162900.48b3421e@free-electrons.com> (raw)
In-Reply-To: <CA+BsyQ4j5udg-jsL-A7Spm6jiDtxfaN4sTF1_MYdbFD7XB8rYQ@mail.gmail.com>
Brendan,
On Wed, 9 Sep 2015 14:58:22 +0100, Brendan Heading wrote:
> > Maybe we could do a similar thing for the binutils package (which is
> > the only other user of the host-texinfo package), and then remove the
> > host-texinfo package altogether. That's obviously a completely separate
> > set of changes.
>
> Why not keep host-texinfo around, even if it is not used by any
> package which is included with buildroot ?
Because we don't like to have host packages that are not used by any
other target packages, as this means this host package is never tested.
This is something that is discussed quite often, recently for the
python-colorama package. I sometimes change my mind a bit on this, it's
hard to be completely clear-cut. For python-colorama, the submitter
came with a potentially interesting use case.
For host-texinfo, if there's nothing that depends on it in Buildroot,
we should simply drop it I believe.
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2015-09-09 14:29 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-09 12:12 [Buildroot] [PATCHv3] gdb: prevent building the documentation Vicente Olivert Riera
2015-09-09 12:42 ` Brendan Heading
2015-09-09 13:49 ` Thomas Petazzoni
2015-09-09 13:58 ` Brendan Heading
2015-09-09 14:29 ` Thomas Petazzoni [this message]
2015-09-09 14:41 ` Vicente Olivert Riera
2015-09-09 14:45 ` Thomas Petazzoni
2015-09-09 14:49 ` Vicente Olivert Riera
2015-09-09 15:14 ` Thomas Petazzoni
2015-09-09 15:29 ` Vicente Olivert Riera
2015-09-09 19:04 ` Arnout Vandecappelle
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=20150909162900.48b3421e@free-electrons.com \
--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