Age | Commit message (Collapse) | Author | Files | Lines |
|
|
|
All checksums have been double-checked against existing RMD160 and
SHA512 hashes
Unfetchable distfiles (fetched conditionally?):
./security/cyrus-sasl/distinfo cyrus-sasl-dedad73e5e7a75d01a5f3d5a6702ab8ccd2ff40d.patch.v2
|
|
|
|
|
|
|
|
|
|
The former now redirects to the latter.
This covers the most simple cases where http://search.cpan.org/dist/name
can be changed to https://metacpan.org/release/name.
Reviewed by hand to hopefully make sure no unwanted changes sneak in.
|
|
|
|
|
|
|
|
Problems found locating distfiles:
Package f-prot-antivirus6-fs-bin: missing distfile fp-NetBSD.x86.32-fs-6.2.3.tar.gz
Package f-prot-antivirus6-ws-bin: missing distfile fp-NetBSD.x86.32-ws-6.2.3.tar.gz
Package libidea: missing distfile libidea-0.8.2b.tar.gz
Package openssh: missing distfile openssh-7.1p1-hpn-20150822.diff.bz2
Package uvscan: missing distfile vlp4510e.tar.Z
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.
|
|
{perl>=5.16.6,p5-ExtUtils-ParseXS>=3.15}:../../devel/p5-ExtUtils-ParseXS
since pkgsrc enforces the newest perl version anyway, so they
should always pick perl, but sometimes (pkg_add) don't due to the
design of the {,} syntax.
No effective change for the above reason.
Ok joerg
|
|
having a PKGNAME of p5-*, or depending such a package,
for perl-5.22.0.
|
|
|
|
|
|
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.
|
|
|
|
|
|
are called p5-*.
I hope that's all of them.
|
|
Bump PKGREVISION.
|
|
|
|
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!
|
|
Upstream changes:
2010-07-03 Release 2.13
Mike McCauley (1):
Fix memory leak in sha1_transform
|
|
- Updating package for p5 module Digest::SHA1 from 2.11 to 2.12
Upstream changes:
2009-05-23 Release 2.12
Gisle Aas (6):
Get rid of the old CVS ids
Avoid "redefined" error for ULONG on Win64
Less optimizations on IRIX [RT#8999]
Clean up the 'git status' output
Mention that SHA-1 might be weak [RT#11880]
Ensure more stuff in the META.yml file [RT#40757]
Steve Peters (1):
Quiet warnings when compiled with -Wwrite-strings [RT#31915]
|
|
block). Uncomment some commented out LICENSE lines while here.
|
|
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=...").
|
|
|
|
can handle packages having no PLIST files.
|
|
|
|
2006-01-18 Gisle Aas
Release 2.11
Internal cleanup to avoid some compiler warnings.
|
|
of Perl files to deal with the perl-5.8.7 update that moved all
pkgsrc-installed Perl files into the "vendor" directories.
|
|
|
|
These paths are now relative to PERL5_PACKLIST_DIR, which currently
defaults to ${PERL5_SITEARCH}. There is no change to the binary
packages.
|
|
|
|
|
|
module directory has changed (eg. "darwin-2level" vs.
"darwin-thread-multi-2level").
binary packages of perl modules need to be distinguishable between
being built against threaded perl and unthreaded perl, so bump the
PKGREVISION of all perl module packages and introduce
BUILDLINK_RECOMMENDED for perl as perl>=5.8.5nb5 so the correct
dependencies are registered and the binary packages are distinct.
addresses PR pkg/28619 from H. Todd Fujinaka.
|
|
Changes since 2.07
==================
Release 2.10
Restore compatibility with perl-5.004 and perl-5.005.
Release 2.09
The 2.08 release did not compile with a threaded debugging
perl, because assert() then needs my_perl. Fixed by commenting
out the asserts.
Release 2.08
Enable PERL_NO_GET_CONTEXT for more more efficient execution
on a threaded perl.
Fix up md5 references. Patch by Ville Skyttä <ville.skytta@iki.fi>.
|
|
|
|
Take maintainership.
Add HOMEPAGE.
Changes since 2.06:
2003-12-05 Gisle Aas <gisle@ActiveState.com>
Release 2.07
Inherit add_bits() from Digest::base if available.
|
|
changes since 2.04:
Release 2.06
The sha1_transform() function did not check that it was actually
passed any arguments.
Complete self-contained documentation included (copied from
Digest::MD5), since the Digest.pm manpage is not always available.
Release 2.05
Added missing cast to support C++ compilation. Patch by Jan Dubois.
Document that the sha1_base64 function and the b64digest method
does not pad their result.
|
|
Don't assume PerlIO_read() works like fread() even though
it was documented like that for perl 5.6. It returns negative
on read failure.
Implemented sha1_transform, required to implement NIST FIPS 186-2.
Make it build on 64-bit platforms with 32-bit longs.
Sync up with the Digest::MD5 implementation:
- added clone method
- addfile croaks if it can't read
- the sha1*() functions warn if called as method
or with reference arguments.
|
|
|
|
|
|
Should anybody feel like they could be the maintainer for any of thewe packages,
please adjust.
|
|
Changes :
- Make it work when there is a mismatch between the
sizeof(BYTEORDER) and sizeof(long). Based on patch
Allen Smith <easmith@beatrice.rutgers.edu>.
- Support UTF8 strings in newer versions of Perl.
|
|
|
|
${PREFIX} -- everything else is pickup up from ${BUILDLINK_DIR}.
|
|
|
|
The automatic truncation in gensolpkg doesn't work for packages which
have the same package name for the first 5-6 chars.
e.g. amanda-server and amanda-client would be named amanda and amanda.
Now, we add a SVR4_PKGNAME and use amacl for amanda-client and amase for
amanda-server.
All svr4 packages also have a vendor tag, so we have to reserve some chars
for this tag, which is normaly 3 or 4 chars. Thats why we can only use 6
or 5 chars for SVR4_PKGNAME. I used 5 for all the packages, to give the
vendor tag enough room.
All p5-* packages and a few other packages have now a SVR4_PKGNAME.
|