in reply to Re^2: Why is it in some other popular languages fewer steps and potential issues when installing libraries no testing needed and no compilation of C/C++ code done
in thread Why are other popular languages very different from Perl when installing libraries, e.g. no testing needed and no compilation of C/C++ code done

If the C library is included with the Perl distribution, CPAN (or App::cpanminus) will kick off the normal C compilation mechanism provided by ExtUtils::MakeMaker, Module::Install or Module::Build, and you will not need any additional interaction.

I'm not sure how things can be made easier than

> cpan DBD::SQLite

[download]

to install, for example, DBD::SQLite.

  • Comment on Re^3: Why is it in some other popular languages fewer steps and potential issues when installing libraries no testing needed and no compilation of C/C++ code done
  • Download Code

Replies are listed 'Best First'.
Re^4: Why is it in some other popular languages fewer steps and potential issues when installing libraries no testing needed and no compilation of C/C++ code done
by hermida (Scribe) on Apr 06, 2011 at 13:40 UTC
    I know, I know, but let me tell you how many people in my community (which is a major user of Perl) think cpan management is too complicated and always ask why in other languages you just get a jar or egg or whatever for dependency management.

    Trust me I'm not complaining at all I am the one who sets up all the CPAN infrastructure for the sysadmins so it is super simple for them to install and upgrade libraries and I have my own local repo and install in my $HOME directory

[reply]

      Ah - then you will need to see the platform specific packages for whatever platform (.ppm for ActiveState Perls, .deb for Debian etc.) you are using. Depending on the kind of platform, you even get management of external dependencies.

[reply]
[reply]

In Section Seekers of Perl Wisdom