[suggest] Perl module request due to latest DBIx::Class release

David Steinbrunner dsteinbrunner at pobox.com
Fri May 15 16:29:13 CEST 2009


Christoph Maser wrote:

> Well Class::Accessor::Grouped is found now  in Version 0.8102. But it is
> giving me this:
> 
> DEBUG: - Test::Builder            ...missing. (would need 0.33)
> DEBUG: - Test::Warn               ...loaded. (0.11 >= 0.11)
> DEBUG: - Test::Exception          ...loaded. (0.27)
> DEBUG: - Test::Deep               ...loaded. (0.100)
> DEBUG: - DBD::SQLite              ...loaded. (1.25 >= 1.23)
> DEBUG: - Data::Page               ...missing. (would need 2)
> DEBUG: - Scalar::Util             ...loaded. (1.19)
> DEBUG: - SQL::Abstract            ...loaded. (1.51 >= 1.51)
> DEBUG: - SQL::Abstract::Limit     ...loaded. (0.141 >= 0.13)
> DEBUG: - Class::C3::Componentised ...missing. (would need 1.0005)
> DEBUG: - Storable                 ...loaded. (2.15)
> DEBUG: - Carp::Clan               ...loaded. (6.00)
> DEBUG: - DBI                      ...loaded. (1.607 >= 1.4)
> DEBUG: - Module::Find             ...loaded. (0.06)
> DEBUG: - Class::Inspector         ...loaded. (1.23)
> DEBUG: - Class::Accessor::Grouped ...loaded. (0.08003 >= 0.08003)
> DEBUG: - JSON::Any                ...loaded. (1.17 >= 1.17)
> DEBUG: - Scope::Guard             ...loaded. (0.03 >= 0.03)
> DEBUG: - Path::Class              ...missing.
> DEBUG: - List::Util               ...loaded. (1.19 >= 1.19)
> DEBUG: - Sub::Name                ...loaded. (0.04 >= 0.04)
> DEBUG: - MRO::Compat              ...loaded. (0.09 >= 0.09)

Aside from Test::Builder, at least most of the other "missing" modules
actually exist.  It is just that they have missing dependencies that cause
they to die when evoked for version numbers.  You can test this by using
this type of command:

perl -MModule::Name -e 'print $Module::Name::VERSION, "\n"'

My notes show that Data::Page is missing Class::Accessor::Chained which in
turn needs Class::Accessor.  Class::C3::Componentised depends on Class::C3,
which resolves, but needs Algorithm::C3, which does not resolve.  If I have
these things installed before trying to install DBIx::Class then all is
good, of course it would be better if all just worked without that step.  I
guess me pointing this out might help you resolve those issues ;-P

Not sure about Path::Class. Is the DBIx::Class spec you are working with
publicly assessable?

As for Test::Builder, it is regrettable but it seems there is not much we
can do here.  Quite frustrating.  The good thing is, it is only for testing
so if there is an otherwise working spec available with properly resolving
dependencies then it is not that hard for someone to build the rpm
themselves.

--
David Steinbrunner





More information about the users mailing list