Commit graph

9 commits

Author SHA1 Message Date
nia
d5c846b3af Update packages using a search.cpan.org HOMEPAGE to metacpan.org.
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.
2019-06-30 20:14:13 +00:00
wiz
9bd737fe76 Recursive bump for perl5-5.28.0 2018-08-22 09:42:51 +00:00
ryoon
1344d8d8e3 Recursive revbump from lang/perl5 5.26.0 2017-06-05 14:22:16 +00:00
wiz
86a78fce2e Bump PKGREVISION for perl-5.24. 2016-06-08 19:22:13 +00:00
agc
d549bff9a5 Add SHA512 digests for distfiles for databases category
Problems found with existing distfiles:
	distfiles/D6.data.ros.gz
	distfiles/cstore0.2.tar.gz
	distfiles/data4.tar.gz
	distfiles/sphinx-2.2.7-release.tar.gz
No changes made to the cstore or mariadb55-client distinfo files.

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.
2015-11-03 01:56:09 +00:00
wen
3eb8fa743b Update to 0.001005
Upstream changes:
0.001005  2015-01-29 17:47:49-06:00 America/Chicago
 - Fix error message for missing values (Thanks Wes Malone!)
2015-08-06 00:15:47 +00:00
wiz
0982effce2 Recursive PKGREVISION bump for all packages mentioning 'perl',
having a PKGNAME of p5-*, or depending such a package,
for perl-5.22.0.
2015-06-12 10:48:20 +00:00
mef
a876fd018a Update 0.001003 to 0.001004
0.001004  2014-11-30 21:50:34-06:00 America/Chicago
 - Fix bug that disallowed false values
2014-12-07 22:06:49 +00:00
wen
a428cabd6b Import DBIx-Introspector-0.001003 as databases/p5-DBIx-Introspector.
DBIx::Introspector is a module factored out of the DBIx::Class
database detection code. Most code that needs to detect which
database it is connected to assumes that there is a one-to-one
mapping from database drivers to database engines. Unfortunately
reality is rarely that simple. For instance, DBD::ODBC is typically
used to connect to SQL Server, but ODBC can be used to connect
to PostgreSQL, MySQL, and Oracle. Additionally, while ODBC is the
most common way to connect to SQL Server, it is not the only option,
as DBD::ADO can also be used.
2014-07-28 00:22:43 +00:00