netfilter-devel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Pablo Neira Ayuso <pablo@netfilter.org>
To: Netfilter Development Mailing list <netfilter-devel@vger.kernel.org>
Cc: netdev@vger.kernel.org, netfilter@vger.kernel.org, lwn@lwn.net,
	netfilter-announce@lists.netfilter.org
Subject: [ANNOUNCE] libmnl 1.0.2 release
Date: Mon, 2 Jan 2012 19:55:36 +0100	[thread overview]
Message-ID: <20120102185536.GA26679@1984> (raw)

[-- Attachment #1: Type: text/plain, Size: 1302 bytes --]

Hi!

The Netfilter project presents libmnl-1.0.0

libmnl is a minimalistic user-space library oriented to Netlink
developers. There are a lot of common tasks in parsing, validating,
constructing of both the Netlink header and TLVs that are repetitive
and
easy to get wrong. This library aims to provide simple helpers that
allows you to re-use code and to avoid re-inventing the wheel.

This library is released under LGPLv2+.

Features:
* Small: the shared library requires around 45KB for an x86-based
* computer.
* Simple: this library avoids complexity and elaborated abstractions
that tend to hide Netlink details.
* Easy to use: the library simplifies the work for Netlink-wise
developers. It provides functions to make socket handling, message
building, validating, parsing and sequence tracking, easier.
* Easy to re-use: you can use the library to build your own
* abstraction
layer on top of this library.
* Decoupling: the interdependency of the main bricks that compose the
library is reduced, i.e. the library provides many helpers, but the
programmer is not forced to use them.

More info at:
http://www.netfilter.org/projects/libmnl/

Doxygen documentation at:
http://www.netfilter.org/projects/libmnl/doxygen/

You can download it via FTP at:
ftp://ftp.netfilter.org/pub/libmnl

Enjoy!

[-- Attachment #2: changes-libmnl-1.0.2.txt --]
[-- Type: text/plain, Size: 1064 bytes --]

Jan Engelhardt (11):
      build: use AM_CPPFLAGS
      build: use only AC_CANONICAL_HOST
      examples/genl: fix newline imbalance
      examples/genl: support dumping the genl families
      src: use limits.h header
      include: use sanitized header from headers_install
      build: abort autogen on subcommand failure
      Update .gitignore
      build: use AC_CONFIG_AUX_DIR and stash away tools
      m4: resolve autoconf-2.68 warnings
      build: disable implicit .tar.gz archive generation and use POSIX mode

Pablo Neira Ayuso (8):
      header: fix invalid use of type void * in arithmetic of mnl_for_each_nest(...)
      Merge branch 'master' of git://dev.medozas.de/libmnl
      doc: don't show up EXPORT_SYMBOL in doxygen
      doxygen: exclude EXPORT_SYMBOL and skip .git files
      COPYING: update file (FSF address was outdated)
      build: kernel-like compilation messages
      example: release them in the public domain
      build: libmnl 1.0.2 release

Sean Robinson (1):
      doc: fix wrong comment describing mnl_nlmsg_batch_stop()


                 reply	other threads:[~2012-01-02 18:55 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20120102185536.GA26679@1984 \
    --to=pablo@netfilter.org \
    --cc=lwn@lwn.net \
    --cc=netdev@vger.kernel.org \
    --cc=netfilter-announce@lists.netfilter.org \
    --cc=netfilter-devel@vger.kernel.org \
    --cc=netfilter@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).