On Sun Oct 15 13:16:05 2006, WYANT wrote:
Show quoted text> The use of VERSION.pm to carry version number seems to be very confusing
> to CPAN, at least on systems where file names are not sensitive to case
> (Mac OS X, VMS, Windows) and where the version pragma
> (
http://search.cpan.org/~jpeacock/version-0.6701/) is installed.
>
> Installation of this package on such systems _may_ clobber the version
> pragma.
>
> I have made this "unimportant" because I don't _know_ that the conflict
> actually happens - but VERSION.pm shows up in blib, so I don't intend to
> install your module to find out.
I'll second that. In fact, I'll amplify it. tidyview is broken on OS X
because of VERSION.pm. It too is cursed with a case-insensitive
filesystem but the special code in TidyView::Options does not take this
into account. Determining filesystem case-sensitivity using $^O is a
bad idea anyway.
PERL_DL_NONLAZY=1 /usr/local/bin/perl "-MExtUtils::Command::MM" "-e"
"test_harness(0, 'blib/lib', 'blib/arch')" lib/PerlTidy/t/*.t
lib/TidyView/t/*.t
lib/PerlTidy/t/Options....ok 1/0Undefined subroutine
&TidyView::Options::qv called at
/usr/local/src/CPAN/tidyview-1.09/blib/lib/TidyView/Options.pm line 68.
INIT failed--call queue aborted.
# Looks like your test died just after 1.
lib/PerlTidy/t/Options....dubious
Test returned status 255 (wstat 65280, 0xff00)
after all the subtests completed successfully
In addition to clashing with version.pm, consider what happens when the
next author gets the idea to ship and install their own VERSION.pm
blowing over yours. Don't hop outside your namespace without good reason.
