Do it for all packages that
* mention perl, or
* have a directory name starting with p5-*, or
* depend on a package starting with p5-
like last time, for 5.18, where this didn't lead to complaints.
Let me know if you have any this time.
a) refer 'perl' in their Makefile, or
b) have a directory name of p5-*, or
c) have any dependency on any p5-* package
Like last time, where this caused no complaints.
to trigger/signal a rebuild for the transition 5.10.1 -> 5.12.1.
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=..."), minus the packages updated after
the perl package update.
sno@ was right after all, obache@ kindly asked and he@ led the
way. Thanks!
Setting license to artistic according to META.yml
Upstream changes:
1.05 Wed Jun 10 20:37:44 CEST 2009
- bugfix: removed a warning on AF_INET6 constant declaration
- update: copyright notice
1.04 Sun Oct 19 17:47:11 CEST 2008
- bugfix: IP_HDRINCL with IPv6 under Linux 2.6.x
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=...").
Pkgsrc changes:
o Canonicalize MASTER_SITES and HOMEPAGE
Upstream changes:
1.03 Fri Mar 21 17:20:00 CET 2008
- added support for IP_HDRINCL with IPv6 raw sockets (Linux only)
=> in fact, it should have worked before, but it appears to be a regression
1.02 Tue Feb 19 12:11:21 CET 2008
- bugfix: due to Socket6 update, AF_INET6 definition has changed
1.01 Sun Feb 17 19:08:15 CET 2008
- update: portability patches for other Unix systems (untested), concerning
IP_HDRINCL constants and the like
- update: license string (lc(Artistic)), to make CPANTS happy
able to write raw data directly to the network. It juste provides three methods
when a Net::Write object has been created for an interface: open, send, close.
It is possible to open a network interface to send frames at layer 2 (you craft
a frame from link layer), or at layer 3 (you craft a frame from network layer),
or at layer 4 (you craft a frame from transport layer).
NOTE: not all operating systems support all layer opening. Currently, Windows
only supports opening and sending at layer 2. Other Unix systems should be able
to open and send at all layers.
