From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v3] pyrex: new package
Date: Sat, 29 Mar 2014 12:03:25 +0100 [thread overview]
Message-ID: <20140329120325.0faa54ca@skate> (raw)
In-Reply-To: <1394920830-12708-1-git-send-email-mlweber1@rockwellcollins.com>
Matt,
On Sat, 15 Mar 2014 17:00:30 -0500, mlweber1 at rockwellcollins.com wrote:
> diff --git a/package/python-pyrex/Config.in.host b/package/python-pyrex/Config.in.host
> new file mode 100644
> index 0000000..4edeb38
> --- /dev/null
> +++ b/package/python-pyrex/Config.in.host
> @@ -0,0 +1,10 @@
> +config BR2_PACKAGE_HOST_PYTHON_PYREX
> + bool "python-pyrex"
> + depends on BR2_PACKAGE_PYTHON
Is it actually really needed to have this host package visible in
menuconfig? python-pyrex is really a tool to generate code, so it
should be used by other packages as a dependency, and does not
necessarily need to be exposed in menuconfig.
To me, host-python-pyrex is a little bit like host-bison or host-flex:
useful as a dependency of another package, but not really useful as a
visible host package in menuconfig.
Would you agree if I removed this option when applying your patch?
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-03-29 11:03 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-15 22:00 [Buildroot] [PATCH v3] pyrex: new package mlweber1 at rockwellcollins.com
2014-03-15 22:25 ` Yann E. MORIN
2014-03-29 11:03 ` Thomas Petazzoni [this message]
2014-03-31 13:01 ` mlweber1 at rockwellcollins.com
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=20140329120325.0faa54ca@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 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.