Opened 5 years ago

Closed 2 years ago

#59801 closed update (fixed)

libnet 1.2

Reported by: ryandesign (Ryan Carsten Schmidt) Owned by: nerdling (Jeremy Lavergne)
Priority: Normal Milestone:
Component: ports Version:
Keywords: Cc: jim@…
Port: libnet, libnet10, libnet11

Description

libnet 1.2 has been released. We should have it in MacPorts. But how?

We currently have a libnet port at version 1.0.2a which about 5 ports depend on, and a libnet11 port at version 1.1.6 which about 10 ports depend on. My understanding is that we need these two different ports because libnet 1.1.x is not compatible with libnet 1.0.x.

However, at least in the opinion of the developer of arping, libnet 1.1.x and libnet 1.2.x are compatible. Therefore I don't think we need a separate port for libnet 1.1.x and libnet 1.2.x.

I think the best solution would be to rename the libnet @1.0.2a port to libnet10, and then to rename the libnet11 @1.1.6 port to libnet, adjusting the dependencies of all the ports that depend on them, and then updating libnet @1.1.6 to 1.2.

It would also be good if, while we're at it, we could make the new libnet10 @1.0.2a port not conflict with the new libnet @1.2 port. libnet10 @1.0.2a should install its files to different locations than the libnet @1.2 port, and the ports that need the old libnet10 should be updated to find the files in those new locations.

We should also examine the 5 ports that depend on libnet 1.0.x. Maybe there are updates available to versions that would be compatible with libnet 1.1.x and later. If all 5 ports can be updated to be compatible with libnet 1.1.x and later, then we wouldn't need a libnet10 port at all anymore.

Change History (6)

comment:1 in reply to:  description Changed 5 years ago by ryandesign (Ryan Carsten Schmidt)

Replying to ryandesign:

We currently have a libnet port at version 1.0.2a which about 5 ports depend on

It was actually 6, because one, libnids, hides its libnet dependency in a variant. But it also already has a variant for libnet 1.1.x support.

$ port file all | sort -u | xargs grep -El ':libnet(\s|$)' | cut -d / -f 7
angst
cdpd
fragrouter
libnids
nemesis
packetforward

and a libnet11 port at version 1.1.6 which about 10 ports depend on.

$ port file all | sort -u | xargs grep -El ':libnet11(\s|$)' | cut -d / -f 7
arping
dnsa
ettercap
libipgeo
libnids
netwib
packit
tcptraceroute
yersinia
syslog-ng

comment:2 Changed 5 years ago by nerdling (Jeremy Lavergne)

Ryan, what's the process for renaming ports again? Leave a stub that indicates "replaced_by"?

Also, do we have any indicator these six/seven libnet0 are still useful to keep in macports?

comment:3 Changed 2 years ago by barracuda156

The current code is on GitHub: https://github.com/libnet/libnet

comment:4 Changed 2 years ago by nerdling (Jeremy Lavergne)

Tempted to just remove the six libnet10 dependents. Sent email to the maintainer of nemesis, all others appear unmaintained and decades out of date.

comment:5 Changed 2 years ago by nerdling (Jeremy Lavergne)

comment:6 Changed 2 years ago by nerdling (Jeremy Lavergne)

Resolution: fixed
Status: assignedclosed
Note: See TracTickets for help on using tickets.