comment on

The issue is that when installed our .pm files will end up in any one of:

  ./
   /usr/local/lib/site_perl
   /etc/perl
   /usr/local/lib/perl/5.10.0
   /usr/local/share/perl/5.10.0
   /usr/lib/perl5
   /usr/share/perl5
   /usr/lib/perl/5.10
   /usr/share/perl/5.10
   /usr/local/lib/site_perl
[download]

We can say: use OurApp::LibName; and find our libs

We can't say my $sql_lib=new SQL::Library {lib=>'sql.lib'}; We have to say: my $sql_lib=new SQL::Library {lib=>'/full/path/to/sql.lib'}

We could write code to search @INC for our file, but that doesn't seem right

There is little or no code in our libraries that is useful outside our application, so publishing to cpan might no make sense. Following the conventions of a cpan package may make our life easier even if we don't ever make a package.

email: mandog

In reply to Re^2: put SQL::Library file where? by mandog
in thread put SQL::Library file where? by mandog

Are you posting in the right place? Check out Where do I post X? to know for sure.
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big> <blockquote> <br /> <dd> <dl> <dt> <em> <font> <h1> <h2> <h3> <h4> <h5> <h6> <hr /> <i> <li> <nbsp> <ol> <p> <small> <strike> <strong> <sub> <sup> <table> <td> <th> <tr> <tt> <u> <ul>
Snippets of code should be wrapped in <code> tags not <pre> tags. In fact, <pre> tags should generally be avoided. If they must be used, extreme care should be taken to ensure that their contents do not have long lines (<70 chars), in order to prevent horizontal scrolling (and possible janitor intervention).
Want more info? How to link or How to display code and escape characters are good places to start.


laziness, impatience, and hubris
	PerlMonks