From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 2/2] python-falcon: new package
Date: Wed, 29 Aug 2018 22:37:01 +0200 [thread overview]
Message-ID: <20180829223701.7a5a0299@windsurf> (raw)
In-Reply-To: <32a0a4a5-a2c4-c42b-50b4-5e618eaf73ef@blach.pl>
Hello,
On Wed, 29 Aug 2018 22:25:30 +0200, Grzegorz Blach wrote:
> If BR2_PACKAGE_HOST_PYTHON_CYTHON is enabled in config, Falcon uses
> Cython to compile own code. Cython on target is not required in this
> case.
OK.
> Settings PYTHON_FALCON_DEPENDENCIES += host-python-cython
> in python-falcon/Config.in also is not required, but may be usable to
> guarantee, that host-python-cython is always installed
> before python-falcon.
Actually our policy is that when a package A can optionally be used by
package B, then package B should have a dependency on package A when
package A is enabled, which is what Joseph was suggesting.
This ensures that package B gets the additional feature
provided/enabled by package A, regardless of the package build order,
and generally makes sure that the features provided by package A
benefits all package that can make use of it.
Best regards,
Thomas
--
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2018-08-29 20:37 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-28 10:16 [Buildroot] [PATCH 1/2] python-mimeparse: new package Grzegorz Blach
2018-08-28 10:16 ` [Buildroot] [PATCH 2/2] python-falcon: " Grzegorz Blach
2018-08-28 10:18 ` Yegor Yefremov
2018-08-28 16:34 ` Joseph Kogut
2018-08-29 19:47 ` Thomas Petazzoni
2018-08-29 20:25 ` Grzegorz Blach
2018-08-29 20:37 ` Thomas Petazzoni [this message]
2018-08-29 21:58 ` Joseph Kogut
2018-08-30 7:31 ` Thomas Petazzoni
2018-08-30 10:20 ` Grzegorz Blach
2018-08-29 19:44 ` Thomas Petazzoni
2018-08-29 19:45 ` Yegor Yefremov
2018-08-28 10:18 ` [Buildroot] [PATCH 1/2] python-mimeparse: " Yegor Yefremov
2018-08-29 19:17 ` Thomas Petazzoni
2018-08-29 19:46 ` Thomas Petazzoni
2018-08-29 20:03 ` Yegor Yefremov
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=20180829223701.7a5a0299@windsurf \
--to=thomas.petazzoni@bootlin.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