in reply to Re^3: Installing a missing module - Perl 5.8.3
in thread Installing a missing module - Perl 5.8.3

Thanks. It's backwards for the OP's needs. It might still work, but it's not guaranteed to work.

Note that $Config{archname} equality isn't enough. That's why I said "all else being equal".

Replies are listed 'Best First'.
Re^5: Installing a missing module - Perl 5.8.3
by syphilis (Archbishop) on Jan 26, 2020 at 23:39 UTC
    Note that $Config{archname} equality isn't enough

    UPDATE: I think I've now figured it out - that you were alluding to the possibility of different toolchain involvement, different external dependencies, etc.

    I didn't know that.
    This would also imply that 2 perls with the same version number and same $Config{archname} could be binary-incompatible.
    For over a quarter of a century, PPM installations have relied entirely (and flawlessly) solely upon version number and $Config{archname} to determine which package to install - and now you're telling me that's insufficient.

    Can you please provide an example of a difference that could cause incompatibility, yet not alter $Config{archname} ?

    Cheers,
    Rob
[reply]

In Section Seekers of Perl Wisdom