in reply to CPAN.pm programming

Why not just put the modules you need in place? Shipping a minicpan and then installing it from said minicpan seems like the long way around.

Replies are listed 'Best First'.
Re^2: CPAN.pm programming
by afoken (Chancellor) on Nov 22, 2009 at 17:54 UTC

    Perhaps because of license issues? For example, DBD::Oracle needs to be linked against Oracle client libraries, but most times, you do not have the permission to redistribute those libraries.

    Alexander

    --
    Today I will gladly share my knowledge and experience, for there are no sweeter words than "I told you so". ;-)
      So? You could still compile DBD::Oracle and distribute it.
Re^2: CPAN.pm programming
by gwhite (Friar) on Nov 23, 2009 at 13:42 UTC

    The nature of the application is that it will be updated pretty regularly with new features that may or may not require CPAN modules. By having a miniCPAN available I can use most any module and not have to worry about dependancies and such. I am sending the client a CD, might as well fill it with what I might need.

    g_White
      But if you're going to update your application, you'll have to send your client something anyway - might as well then send the modules you need. You also may need a module, or a version of a module that wasn't present in the minicpan you deliver on CD.

        Right, but I usually send updates zipped via email. And sending a module doesn't mean you might not forget a depndant module. This works for me.

        g_White