I feel pretty meek saying this, given you probably already know this, James, but my approach would be to leave the source tree sacrosanct and put your newer module in some other place and then make sure that other place is higher up in the @INC list.<br>
<br>In the past, I've been banging my head in trying to build debian packages for more up-to-date perl modules (it's sad how out-of-date they can get) and Cees Hek finally hammered cpan (cpanplus, really) into me where it won't mess w/ the debian "core." So when I want to get a Perl module, I <b>cpanp</b> it and it installs somewhere else (/usr/local/share/perl/5.8.8), overriding the out-of-date version that Debian has.<br>
<br>Cheers,<br><br>Jason<br><br><div class="gmail_quote">On Wed, Feb 4, 2009 at 2:31 PM, James Olin Oden <span dir="ltr"><<a href="mailto:james.oden@gmail.com">james.oden@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
HI All,<br>
<br>
Does anyone understand the source tree of a typical perl distribution?<br>
I'm trying to figure out how to integrate a newer module into an<br>
existing perl distribution (i.e. into its source tree) but I'm finding<br>
whereas the cpan module is self contained under one directory the<br>
sources in the perl distribution are not, splitting some files under<br>
the ext directory and some under the lib directory. Ultimately, I'm<br>
just trying to figure out how the the perl distribution build works in<br>
regards to perl modules. Does anyone understand this and/or know of<br>
documentation that would help with this.<br>
<br>
Thanks...james<br>
_______________________________________________<br>
Raleigh-talk mailing list<br>
<a href="mailto:Raleigh-talk@pm.org">Raleigh-talk@pm.org</a><br>
<a href="http://mail.pm.org/mailman/listinfo/raleigh-talk" target="_blank">http://mail.pm.org/mailman/listinfo/raleigh-talk</a><br>
</blockquote></div><br>