public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Mike Frysinger <vapier@gentoo.org>
To: gentoo-dev@gentoo.org
Subject: [gentoo-dev] deprecating libnet-1.0.x (it's about time)
Date: Tue, 19 Aug 2003 16:56:50 -0400	[thread overview]
Message-ID: <200308191656.50226.vapier@gentoo.org> (raw)

libnet-1.0.x has been deprecated for sometime (well, since 1.1.x has been 
releeased), but we still were using libnet-1.0.x as the only libnet in 
portage ... reason being that many (well the majority) of apps that use 
libnet use libnet-1.0 ...
unfortunately, 1.0.x and 1.1.x are not API compatible ...

i just released a short time ago libnet versions that SLOT into 1.0 and 1.1 
... right now, libnet-1.0 occupies the 'default' position (libnet.a, 
libnet.h, libnet-config, etc...) while libnet-1.1 occupies libnet-1.1.a and 
libnet-1.1.h ... i would like to switch that around and patch all the apps 
that use libnet-1.0.x to point to the 'old' libnet location (-lnet becomes 
-lnet-1.0, libnet-config becomes libnet-1.0-config, etc...) ...
the benefits (for those who havent caught on yet):
rather than constantly maintaining patches for new apps that use 1.1, we only 
have to patch once (see below) for the 1.0 apps

the good news !
first: libnet is a static library, thus all your install apps will not be 
affected :D
second: if a libnet app tries to link against the wrong libnet, you *will* 
know :)  they bomb out with some sweet compile/linker errors
third: ive already made the ebuilds to put libnet-1.0.x into the 'deprecated' 
position and to put libnet-1.1.x into the 'regular' position
fourth: ive already made the patches against all libnet-1.0.x apps in portage 
:D
fifth: umm, it's a good thing

the bad news !
well, none really ... but if you help maintain any of the following apps i'd 
like to hear about it since ive got a patch for your source:
net-analyzer/angst
net-analyzer/arping (has 1.0 and 1.1 version)
net-analyzer/dsniff
net-analyzer/egressor
net-analyzer/hogwash (this needs a lot of work ...)
net-analyzer/isic
net-analyzer/paketto (well not really, it uses a bundled libnet)
net-analyzer/snort (has 1.0 and 1.1 version)
net-analyzer/tcptraceroute
net-analyzer/zodiac
net-dns/dnshijacker
net-libs/libnids (this is SLOT-ed now too since it works with 1.0 and 1.1)
net-libs/libnet
net-misc/nemesis
net-misc/rarpd
sys-cluster/heartbeat

i'd like to roll these changes into ~ (and well, afaik, all i gotta do is 
commit these ebuilds in my local portdir) soon

feedback is welcome :)
-mike


--
gentoo-dev@gentoo.org mailing list


             reply	other threads:[~2003-08-19 20:56 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-08-19 20:56 Mike Frysinger [this message]
2003-08-19 21:12 ` [gentoo-dev] deprecating libnet-1.0.x (it's about time) Brian Jackson
2003-08-19 22:19 ` Ned Ludd
2003-08-19 22:35   ` Mike Frysinger
2003-08-21  5:21 ` [gentoo-dev] libnet-1.0.x is now deprecated in unstable Mike Frysinger

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=200308191656.50226.vapier@gentoo.org \
    --to=vapier@gentoo.org \
    --cc=gentoo-dev@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