Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>Well, it all depends on the intended use of the modules.</p> <p>The native package management has many advantages:</p> <ul> <li>The Perl modules will integrate perfectly with your system, e.g. files are in the right (system-dependant) place, scripts added to the PATH, etc.</li> <li>Automatic upgrades and security patching.</li> <li>Probably a maintainer or maintainer group that care about your modules (e.g. the Debian Perl group).</li> <li>Distribution-specific bugs can be fixed before reaching mainstream (that may or not have the platform specific knowledge).</li> <li>When deploying to machines with the same OS-version, you can take the packages dependencies for granted.</li> </ul> <p>When installing directly from CPAN, you also have some advantages:</p> <ul> <li>You can install the latest release of the module.</li> <li>You can install an specific version (older or developers's release) of the module.</li> <li>You can fine-tune the compilation or installation parameters of the module.</li> </ul> <p>Nowadays, <a href="http://search.cpan.org/perldoc?local%3a%3alib" rel="nofollow">local::lib</a> and <a href="http://search.cpan.org/perldoc?App%3a%3aperlbrew" rel="nofollow">perlbrew</a> (<a href="http://nxadm.wordpress.com/2010/12/10/get-the-latest-perl-release-with-perlbrew/" rel="nofollow">howto</a>) has made the CPAN way a lot more interesting for a developer. <a href="http://search.cpan.org/perldoc?local%3a%3alib" rel="nofollow">local::lib</a> lets you have your private module tree while using the system's perl binary and <a href="http://search.cpan.org/perldoc?App%3a%3aperlbrew" rel="nofollow">perlbrew</a> lets you easily create your own complete Perl installations (also several Perl releases in parallel).</p> <p>Both ways are valid, and as said, the advantage depends on the intended usage. </p>
    singulars
    1. This table or related slice is empty.
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. VO
      singulars
      1. This table or related slice is empty.
    2. VO
      singulars
      1. This table or related slice is empty.
    3. VO
      singulars
      1. This table or related slice is empty.
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload