public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Bjarke Istrup Pedersen <gurligebis@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] RFC: Having a seperate package for libiptc
Date: Sat, 25 Oct 2008 02:50:30 +0200	[thread overview]
Message-ID: <49026D56.5030306@gentoo.org> (raw)
In-Reply-To: <20081024235619.GC23818@curie-int.orbis-terrarum.net>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Robin H. Johnson skrev:
| On Sat, Oct 25, 2008 at 12:52:40AM +0200, Bjarke Istrup Pedersen wrote:
|> What do you think - Should I add this library ebuild to the tree, or
|> should I just give up getting miniupnpd added to the tree, since there
|> is no alternative to using libiptc?
|> I already have an ebuild for it that compiles iptables, and just
|> installs the headers and library files, and my local tests shows that it
|> works fine here.
| Unless vapier has a strong reason not to include libiptc, you should
| rather just modify the main iptables ebuild to install the library
| again.
|
| Adding a separate variant of the package just for the library is a sure
| way to cause missed security patches and bugfixes later on (see shades
| of xpdf).
|

Okay, I'll ask him for input on it :)
Thanks.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iEYEARECAAYFAkkCbVYACgkQO+Ewtpi9rLGlyQCgrNJ9gD6TzhHtkluBGEx0jOav
Z/IAn35vLZ6DClVNZ1HTh+tR7RtJL5qY
=IEgt
-----END PGP SIGNATURE-----



      reply	other threads:[~2008-10-25  0:51 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-10-24 22:52 [gentoo-dev] RFC: Having a seperate package for libiptc Bjarke Istrup Pedersen
2008-10-24 23:56 ` Robin H. Johnson
2008-10-25  0:50   ` Bjarke Istrup Pedersen [this message]

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=49026D56.5030306@gentoo.org \
    --to=gurligebis@gentoo.org \
    --cc=gentoo-dev@lists.gentoo.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