If the SQL::Library isn't for CPAN, then it is more of an layer of the app above the CPAN modules used (or currently being refactored out from old code).
Can you think/structure app + SQL::Library as a kind of 'user' providing code or code refs for use in hook functions provided by lower level modules? Alternatively, with similar effect: can you think of this as sub-classing the cpan modules?
If I correctly see the issue, shouldn't such an approach solve at least the 'future CPAN module depending on external files not in CPAN'?
ps: if you've split the modules in one for CPAN, one for internal use and both are installing in @INC following CPAN guidelines, why do you need an explicit search of @INC? Unless for instance-specific templates. And that would be application-instance-specific app-configuration, and not use Perl's @INC at all.
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:
You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
- a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, 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, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.
| & || & |
| < || < |
| > || > |
| [ || [ |
| ] || ] ||