From: Michael Olbrich <m.olbrich@pengutronix.de>
To: ptxdist@pengutronix.de
Cc: "Alexander Aring" <aar@pengutronix.de>,
"Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>
Subject: Re: [ptxdist] iproute2 dependencies
Date: Mon, 17 Oct 2016 15:21:08 +0200 [thread overview]
Message-ID: <20161017132108.q45v4ymdpym7piay@pengutronix.de> (raw)
In-Reply-To: <20161017131349.z6vdkfnnw3cvzkpo@pengutronix.de>
Hi,
On Mon, Oct 17, 2016 at 03:13:49PM +0200, Michael Olbrich wrote:
> On Mon, Oct 17, 2016 at 02:54:51PM +0200, Uwe Kleine-König wrote:
> > On Mon, Oct 17, 2016 at 12:48:37PM +0200, Clemens Gruber wrote:
> > > What's also interesting to me is that Debian does not depend on
> > > libxtables11, it is only recommended.
> > Looking at iproute2 4.6.0-4, it build-depends on iptables-dev though. So
> > maybe only the headers are needed, but not the library?!
> >
> > In the changelog there is:
> >
> > iproute (20121001-2) experimental; urgency=low
> >
> > * Generate recommends for optional module dependencies
> > This makes the optional module dependency on libxtables more
> > visible, to hopefully get iproute rebuilt whenever libxtables bumps
> > soname.
> > Thanks to iptables maintainer for splitting libxtables9 into
> > a separate package in version 1.4.16.3-2.
> >
> > Maybe this is also related?
>
> Somewhat. The situation is like this:
> iproute has plugins that are loaded at runtime with dlopen. Some of them
> need libxtables. So unless these plugins are actually used libxtables is
> not needed. So libxtables a optional _runtime_ dependency but to build a
> working plugin its a required _buildtime_ dependency.
>
> The current code is rather broken. It has some imported iptables headers
> (from version 1.6.0), but those are useless because xtables-version.h is
> missing...
Clemens: I think a patch that adds xtables-version.h is the cleanest
solution. The resulting m_xt.so will be broken because it doesn't link to
libiptables but we don't install that right now.
If someone wants it we can add the dependency and install the plugin.
Michael
--
Pengutronix e.K. | |
Industrial Linux Solutions | http://www.pengutronix.de/ |
Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
_______________________________________________
ptxdist mailing list
ptxdist@pengutronix.de
next prev parent reply other threads:[~2016-10-17 13:21 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-17 10:48 Clemens Gruber
2016-10-17 12:54 ` Uwe Kleine-König
2016-10-17 13:13 ` Michael Olbrich
2016-10-17 13:21 ` Michael Olbrich [this message]
2016-10-17 15:23 ` Clemens Gruber
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=20161017132108.q45v4ymdpym7piay@pengutronix.de \
--to=m.olbrich@pengutronix.de \
--cc=aar@pengutronix.de \
--cc=ptxdist@pengutronix.de \
--cc=u.kleine-koenig@pengutronix.de \
/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