Skip Menu |

This queue is for tickets about the CPAN-SQLite CPAN distribution.

Report information
The Basics
Id: 83818
Status: resolved
Worked: 10 min
Priority: 0/
Queue: CPAN-SQLite

People
Owner: stro [...] cpan.org
Requestors: arfreitas [...] cpan.org
Cc:
AdminCc:

Bug Information
Severity: Unimportant
Broken in: 0.202
Fixed in: 0.203



Subject: POD error in SQLite.pm
There is a small POD error in SQLite.pm regarding a link to the CPAN module: cpan[2]> install CPAN::SQLite Running install for module 'CPAN::SQLite' Running make for S/ST/STRO/CPAN-SQLite-0.202.tar.gz Checksum for /cygdrive/c/minicpan/authors/id/S/ST/STRO/CPAN-SQLite-0.202.tar.gz ok Scanning cache /home/slh2170/.cpan/build for sizes ............................................................................DONE CPAN.pm: Building S/ST/STRO/CPAN-SQLite-0.202.tar.gz Created MYMETA.yml and MYMETA.json Creating new 'Build' script for 'CPAN-SQLite' version '0.202' (/usr/bin/perl Build.PL exited with 0) CPAN::Reporter: Build.PL result is 'pass', No errors. ./Build: blib/lib/CPAN/SQLite/DBI.pm: cannot resolve L<DBI> in paragraph 21. ./Build: blib/lib/CPAN/SQLite.pm: cannot resolve L<cpandb> in paragraph 60. I attached a patch to fix it. This type of error can be avoid with the automated tests includes Test::Pod. Adding a automatic test with Test::Pod is really simple: just include the pod.t in the test directory of the distribution and all the POD's will be tests. Of course, is necessary to include Test::Pod as a dependency to do that. Regards, Alceu
Subject: pod.t
use Test::More; eval "use Test::Pod 1.00"; plan skip_all => "Test::Pod 1.00 required for testing POD" if $@; all_pod_files_ok();
Subject: patch.txt
--- /usr/lib/perl5/site_perl/5.14/CPAN/SQLite.pm 2013-03-07 11:55:28.000000000 -0300 +++ /cygdrive/c/temp/SQLite.pm 2013-03-07 14:41:56.783761400 -0300 @@ -137,7 +137,7 @@ day old. If the C<CPAN> option is not given, it will default -to C<cpan_home> of L<CPAN::>, if this is configured, +to C<cpan_home> of L<CPAN>, if this is configured, with the index files found under C<keep_source_where>. A fatal error results if such a directory isn't found. Updates to these index files are assumed here to be @@ -258,7 +258,7 @@ L<CPAN::SQLite::Index>, for setting up and maintaining the database, and L<CPAN::SQLite::Search> for an interface to querying the database. Some details -of the interaction with L<CPAN::> is available from +of the interaction with L<CPAN> is available from L<CPAN::SQLite::META>. See also the L<cpandb> script for a command-line interface to the indexing and querying of the database. @@ -307,7 +307,7 @@ at this time, the latest version of the I<libwww-perl> distribution on CPAN is 5.805, but there are modules such as I<URI::URL::finger> contained in version 5.10 of libwww-perl that are not present in 5.805. -This behaviour differs from that of L<CPAN::> without CPAN::SQLite. +This behaviour differs from that of L<CPAN> without CPAN::SQLite. This may change in the future. Please report bugs and feature requests via
POD should be fixed in 0.203. As for including POD test: I wouldn't do this. My rationale is: regular tests should only check functionality and no POD syntax, POD coverage, perlcritic, line feeds etc. All these things could potentially break cpan installation because of failing and that's very inconvenient for user. I've seen pod.t/podc.t failures when Test::Pod or Test::Pod::Coverage was at some buggy version, critic is even worse as someone may install some custom rule. I'm converting this package to use Dist::Zilla, so I'll run these tests before releasing a new version though. -- Serguei Trouchelle