CVS log for pkgsrc/net/p5-Net-Write/distinfo

Up to [cvs.NetBSD.org] / pkgsrc / net / p5-Net-Write

Request diff between arbitrary revisions

Keyword substitution: kv
Default branch: MAIN

net: Replace RMD160 checksums with BLAKE2s checksums

All checksums have been double-checked against existing RMD160 and
SHA512 hashes

Not committed (merge conflicts...):

net/radsecproxy/distinfo

The following distfiles could not be fetched (fetched conditionally?):

./net/citrix_ica/distinfo citrix_ica-10.6.115659/en.linuxx86.tar.gz
./net/djbdns/distinfo dnscache-1.05-multiple-ip.patch
./net/djbdns/distinfo djbdns-1.05-test28.diff.xz
./net/djbdns/distinfo djbdns-1.05-ignoreip2.patch
./net/djbdns/distinfo djbdns-1.05-multiip.diff
./net/djbdns/distinfo djbdns-cachestats.patch

net: Remove SHA1 hashes for distfiles

Add SHA512 digests for distfiles for net category

Problems found with existing digests:
	Package haproxy distfile haproxy-1.5.14.tar.gz
	159f5beb8fdc6b8059ae51b53dc935d91c0fb51f [recorded]
	da39a3ee5e6b4b0d3255bfef95601890afd80709 [calculated]

Problems found locating distfiles:
	Package bsddip: missing distfile bsddip-1.02.tar.Z
	Package citrix_ica: missing distfile citrix_ica-10.6.115659/en.linuxx86.tar.gz
	Package djbdns: missing distfile djbdns-1.05-test25.diff.bz2
	Package djbdns: missing distfile djbdns-cachestats.patch
	Package djbdns: missing distfile 0002-dnscache-cache-soa-records.patch
	Package gated: missing distfile gated-3-5-11.tar.gz
	Package owncloudclient: missing distfile owncloudclient-2.0.2.tar.xz
	Package poink: missing distfile poink-1.6.tar.gz
	Package ra-rtsp-proxy: missing distfile rtspd-src-1.0.0.0.tar.gz
	Package ucspi-ssl: missing distfile ucspi-ssl-0.70-ucspitls-0.1.patch
	Package waste: missing distfile waste-source.tar.gz

Otherwise, existing SHA1 digests verified and found to be the same on
the machine holding the existing distfiles (morden).  All existing
SHA1 digests retained for now as an audit trail.

Update to 1.10
--------------
1.10 Wed Mar  4 07:15:18 CET 2015
   - bugfix: fallback on using Socket::GetAddrInfo for getaddrinfo()

Update 1.07 to 1.09
-------------------
1.09 Sun Feb 15 18:06:48 CET 2015
   - update: EUID 0 check is done at open() call instead of new() call
   - bugfix: take inet_pton() and getaddrinfo() from Socket if available, or from Socket6
   - tests: added tests 02 and 03 to test if inet_pton() and N:W:L3 open() are working

1.08 Fri Jan 23 07:53:16 CET 2015
   - bugfix: on setting AF_INET6(), and makes Socket6 module optional
   => thanks to Vince
   - update: copyright notice
   - update: Kwalitee

Update to 1.07 based on PR 47628 by Edgar Fuß.

1.07 Sun Sep  2 18:42:02 CEST 2012
   - bugfix: returns true when _check() is ok

Update to 1.06

Upstream changes:
1.06 Sat Sep  1 12:45:09 CEST 2012
   - update: better error handling scheme
   - update: copyright notice

Updating package for p5 module Net::Write from 1.03nb1 to 1.05
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

Update from version 1.00 to 1.03, discussed in general terms with maintainer.

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

Net::Write provides a portable interface to open a network interface, and be
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.

Initial revision