Thanks for your initiative to resolve issues you encountered.
The installation of Package::Transporter requires mro and in theory
there could be a suitable mro.pm for 5.8-. In that sense the answer to
your original answer is no, it's not about lucky numbers. The module
will work if there is a mro.pm installed, which is checked for during
installation.
Practically you recommend to use MRO::Compat by default instead of mro.
I've changed the subject accordingly.
Right now that module is suggested in the INSTALL file and the manual
page for pre-5.10 Perl installations. It even used to be in
Package::Transporter::Standard, but commented and not activated.
I'm fully supporting more straightforward solutions, e.g. a mro.pm in
5.8-. So that the interface is simply 'use mro', regardless of the
version of Perl5 installed.
Imagine every module had to be loaded with a ::Compat suffix, like
strict::Compat in 5.10+ just to bring a better strict.pm to 5.003. The
current concept of MRO::Compat produces more cruft than compatibility,
because the number of past versions is limited, while future versions
are potentially unlimited. It projects itself into all lively future
versions, while it has direct benefits only for past and mostly dead
versions.
In that sense MRO::Compat is by no means a 'noop' in the area of module
functions. A module is more than a skip-able internal hook.
In short, I'm not going to ask 5.10+ users to install modules for 5.8-
installations. It's a crying imbalance. This issue isn't specifically
related to Package::Transporter, so I'd like to close this ticket. Thank
you.
