G'day charithd,

Having control over which versions of modules your clients are using can actually be a boon (rather than an onerous responsibility). It can save a lot headaches with version incompatibility between software on different machines. It also removes your reliance on the client doing the right thing which, in my experience, is fraught with problems.

Having said that, neither DBI nor DBD::Oracle are pure Perl modules: both require compilation. So, the task is somewhat more complicated than just copying some *.pm files to certain locations.

What you possibly could do would be to distribute the source for those modules and provide an installation shell script which can be run on each machine that requires it. This is something I've done in the past with many modules and, in general, it's worked well.

Installation of DBI is fairly straigtforward and should be easy to script. It's been quite some time since I installed DBD::Oracle, so I can't really comment on that (although I do seem to remember doing something along these lines with this module many years ago): you've probably got current knowledge and a much better idea of what's involved that I do.

-- Ken

In reply to Re: [perl|DBI] packaging tool with DBI and DBD::Oracle by kcott
in thread [perl|DBI] packaging tool with DBI and DBD::Oracle by charithd

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.