From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 3/3] package/nginx-naxsi: add missing pcre dependency
Date: Wed, 14 Sep 2016 13:45:12 +0200 [thread overview]
Message-ID: <20160914134512.5d8a1e91@free-electrons.com> (raw)
In-Reply-To: <c4abd31c-7224-7d6f-a3b0-cb1ce295caa9@mind.be>
Hello,
On Tue, 13 Sep 2016 19:30:19 +0200, Arnout Vandecappelle wrote:
> > Nope, this is not needed.
> > naxsi is a nginx' module, built by nginx.mk, which already has an
> > automatic dependency on pcre when selected.
>
> I don't think we should rely on transitive dependencies. naxsi.h #include's
> pcre.h, so there should be an explicit dependency in the .mk file.
>
> Whenever you don't have that, the 'select' in Config.in should carry a comment
> explaining why not (usually 'runtime dependency').
It's not a transitive dependency here. The interaction between
nginx-naxsi and nginx is very special: nginx-naxsi is only in charge of
downloading source code, and provide it to nginx during its build
process. nginx is the one that *depends* on nginx-naxsi, so that
nginx-naxsi has downloaded and extracted its source code before nginx
gets configured.
So, nginx-naxsi is the one that really needs pcre (so it makes sense
for it to select pcre). But it terms of build ordering, pcre is only
really needed before nginx starts its configuration step.
So I believe the current situation is OK, with the exception that
nginx-naxsi/Config.in should have a comment that explains that.
Thanks,
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com
next prev parent reply other threads:[~2016-09-14 11:45 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-12 19:23 [Buildroot] [PATCH 1/3] package/urg: fix build Samuel Martin
2016-09-12 19:23 ` [Buildroot] [PATCH 2/3] package/urg: fix build with gcc-6 Samuel Martin
2016-09-12 20:41 ` Thomas Petazzoni
2016-09-13 4:19 ` Samuel Martin
2016-09-13 6:38 ` Arnout Vandecappelle
2016-10-15 10:24 ` Thomas Petazzoni
2016-09-12 19:23 ` [Buildroot] [PATCH 3/3] package/nginx-naxsi: add missing pcre dependency Samuel Martin
2016-09-12 20:39 ` Thomas Petazzoni
2016-09-13 6:40 ` Arnout Vandecappelle
2016-09-13 7:57 ` Samuel Martin
2016-09-13 17:30 ` Arnout Vandecappelle
2016-09-13 17:52 ` Samuel Martin
2016-09-14 11:45 ` Thomas Petazzoni [this message]
2016-09-12 20:41 ` [Buildroot] [PATCH 1/3] package/urg: fix build Thomas Petazzoni
2016-09-14 9:47 ` Thomas Petazzoni
2016-09-15 4:37 ` Samuel Martin
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=20160914134512.5d8a1e91@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