to trigger/signal a rebuild for the transition 5.8.8 -> 5.10.0.
The list of packages is computed by finding all packages which end
up having either of PERL5_USE_PACKLIST, BUILDLINK_API_DEPENDS.perl,
or PERL5_PACKLIST defined in their make setup (tested via
"make show-vars VARNAMES=...").
In Brief:
3.24 Sat Dec 16 17:48:15 CET 2006
- NEW: now supports big-endian archs (IPv4 and IPv6 update)
- bugfix: Frame: require VLAN
3.21 Wed Nov 15 19:52:43 CET 2006
- NEW: added layers STP, OSPF (header only), IGMPv4 (v1 and v2),
CDP::Address, CDP::TypeAddresses, CDP::TypeCapabilities,
CDP::TypePortId, CDP::TypeSoftwareVersion
- NEW: Dump now support PPP links
3.20 Sun Nov 12 23:02:09 CET 2006
- NEW: support for PPPoE, PPP, PPPLCP, LLC, and begin the work for CDP
RECOMMENDED is removed. It becomes ABI_DEPENDS.
BUILDLINK_RECOMMENDED.foo becomes BUILDLINK_ABI_DEPENDS.foo.
BUILDLINK_DEPENDS.foo becomes BUILDLINK_API_DEPENDS.foo.
BUILDLINK_DEPENDS does not change.
IGNORE_RECOMMENDED (which defaulted to "no") becomes USE_ABI_DEPENDS
which defaults to "yes".
Added to obsolete.mk checking for IGNORE_RECOMMENDED.
I did not manually go through and fix any aesthetic tab/spacing issues.
I have tested the above patch on DragonFly building and packaging
subversion and pkglint and their many dependencies.
I have also tested USE_ABI_DEPENDS=no on my NetBSD workstation (where I
have used IGNORE_RECOMMENDED for a long time). I have been an active user
of IGNORE_RECOMMENDED since it was available.
As suggested, I removed the documentation sentences suggesting bumping for
"security" issues.
As discussed on tech-pkg.
I will commit to revbump, pkglint, pkg_install, createbuildlink separately.
Note that if you use wip, it will fail! I will commit to pkgsrc-wip
later (within day).
layers 2, 3, 4 and 7.
Basically, you forge each layer of a frame (Net::Packet::IPv4 for layer 3,
Net::Packet::TCP for layer 4 ; for example), and pack all of this into a
Net::Packet::Frame object. Then, you can send the frame to the network, and
receive it easily, since the response is automatically searched for and
matched against the request.
