From: Antonio Quartulli <antonio@meshcoding.com>
To: Sven Eckelmann <sven@narfation.org>
Cc: The list for a Better Approach To Mobile Ad-hoc Networking
<b.a.t.m.a.n@lists.open-mesh.org>
Subject: Re: [B.A.T.M.A.N.] [PATCH 0/3] batctl: Use libnl(-tiny) for netlink communication
Date: Thu, 16 Jan 2014 22:11:38 +0100 [thread overview]
Message-ID: <52D84B0A.10208@meshcoding.com> (raw)
In-Reply-To: <6312194.LhI8hzXjyH@bentobox>
[-- Attachment #1: Type: text/plain, Size: 1174 bytes --]
Hi Sven,
On 06/01/14 20:35, Sven Eckelmann wrote:
> Hi,
>
> the current release 2014.0.0 made some problems for me because Debian the new
> function "rtnl_open" conflicted with libnl-3.0. libnl-3.0 was used in the
> Debian package to follow the Debian policy chapter 4 about duplicated code.
>
> Using libnl should not be a problem for any linux system because everyone uses
> it when wireless configuration is done. For example libnl-tiny is already used
> by the normal OpenWrt system in base system packages:
I think that it may still be the case that we want to compile batctl on
an host without libnl.
In the end batman-adv can run on Ethernet and we may have an embedded
system with no wifi which has no libnl at all.
I was wondering....what if we check if libnl is installed or not and in
case it is missing we disable the address translation and vlan operations?
In this way we can add the dependency to libnl and avoid code
duplication but at the same time we keep libnl-free users happy.
I think batctl can be useful for many things, also if libnl is not
installed.
What do you think?
Cheers,
--
Antonio Quartulli
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2014-01-16 21:11 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-06 19:35 [B.A.T.M.A.N.] [PATCH 0/3] batctl: Use libnl(-tiny) for netlink communication Sven Eckelmann
2014-01-06 19:37 ` [B.A.T.M.A.N.] [PATCH 1/3] batctl: Avoid name clash "rtnl_open" with libnl Sven Eckelmann
2014-01-06 19:37 ` [B.A.T.M.A.N.] [PATCH 2/3] batctl: Use libnl to implement mac resolver Sven Eckelmann
2014-01-23 8:21 ` Marek Lindner
2014-01-06 19:37 ` [B.A.T.M.A.N.] [PATCH 3/3] batctl: Use libnl to implement vlan parent device resolver Sven Eckelmann
2014-01-27 6:22 ` Marek Lindner
2014-01-23 7:28 ` [B.A.T.M.A.N.] [PATCH 1/3] batctl: Avoid name clash "rtnl_open" with libnl Marek Lindner
2014-01-16 21:11 ` Antonio Quartulli [this message]
2014-01-17 9:37 ` [B.A.T.M.A.N.] [PATCH 0/3] batctl: Use libnl(-tiny) for netlink communication Sven Eckelmann
2014-01-19 10:20 ` Antonio Quartulli
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=52D84B0A.10208@meshcoding.com \
--to=antonio@meshcoding.com \
--cc=b.a.t.m.a.n@lists.open-mesh.org \
--cc=sven@narfation.org \
/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