All of lore.kernel.org
 help / color / mirror / Atom feed
From: Eric Leblond <eric@inl.fr>
To: Pablo Neira Ayuso <pablo@netfilter.org>
Cc: netfilter-devel@vger.kernel.org
Subject: Re: [ULOGD2 PATCH 2/3] Make NFLOG and NFCT build conditionnal
Date: Fri, 12 Sep 2008 08:53:22 +0200	[thread overview]
Message-ID: <20080912065322.GD20985@ice-age> (raw)
In-Reply-To: <48C99D1E.3010506@netfilter.org>

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

Hi,

On Friday, 2008 September 12 at  0:35:10 +0200, Pablo Neira Ayuso wrote:
> Eric Leblond wrote:
> > Hello,
> > 
> > On Thursday, 2008 September 11 at 23:56:57 +0200, Pablo Neira Ayuso wrote:
> >> Eric Leblond wrote:
> >>> This patch modifies the build system behaviour to be able to compile
> >>> ulogd on system without recent release of libnetfilter library. If
> >>> a library is absent or too old, it will simply not compile the concerned
> >>> input module.
> >> I don't see any gain from this patch. We had this sort of conditional
> >> compilation in iptables - that we finally removed - and it was source of
> >> user-side problems.
> > 
> > Hmm, even if you think autodetection is a mistake, it is useful to
> > be able to compile ulogd on system where NFLOG or NFCT is not installed
> > or not usable (too old kernel).
> 
> We're having this discussion over and over again :), ulogd is intended
> for new systems. The ULOG target support should be legacy. You know how
> limited the ULOG target is, and how many headache gives to add new
> features to it ;)

Yes :). I was not thinking about maintaining ULOG support when doing the
work for this patch.

> > What do you think about a --without flag to be able to manually disable
> > the compilation ?
> 
> Well, I'd prefer that but, sincerely, your obsession with legacy systems
> go really that far.

Not as far as Harald's one who put this feature in the TODO list ;)

But, my point was not really intendend to address legacy systems. I just
want to have something clean for people who for example want only to use NFLOG.
That will be stupid for them to compile and install libnetfilter_conntrack
on their system and not to use it.

BR,
-- 
Eric Leblond
INL: http://www.inl.fr/
NuFW: http://www.nufw.org/

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

  reply	other threads:[~2008-09-12  6:53 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-09-11 20:48 [ULOGD2 PATCH 2/3] Make NFLOG and NFCT build conditionnal Eric Leblond
2008-09-11 21:56 ` Pablo Neira Ayuso
2008-09-11 22:15   ` Eric Leblond
2008-09-11 22:35     ` Pablo Neira Ayuso
2008-09-12  6:53       ` Eric Leblond [this message]
2008-09-12 11:02         ` Pablo Neira Ayuso
2008-09-13 11:13           ` [ULOGD2 PATCH] Add flags to disable NFLOG or NFCT at configure time Eric Leblond
2008-09-12  2:39     ` [ULOGD2 PATCH 2/3] Make NFLOG and NFCT build conditionnal Jan Engelhardt

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=20080912065322.GD20985@ice-age \
    --to=eric@inl.fr \
    --cc=netfilter-devel@vger.kernel.org \
    --cc=pablo@netfilter.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.