Ken Moffat wrote these words on 12/11/12 19:28 CST: > Sounds nice, but what about when a newer version of a module > suddenly brings in a whole load of extra dependencies ?
That would be the case in any update. Problem is that CPAN typically deletes old versions, and that requires users to find and install updated versions. I have extensive experience with Perl Modules and have found that they are very backwards compatible. What worked in the past typically works going forward. In the case of LWP (which you mentioned), I have made significant updates to that portion of the Perl Module page, and I am confident that the new instructions I will commit will work for some time. My point with this thread is hard-coded versions of Perl Modules may not exist (other than on Anduin), and this could allow for bugs to exist if users install old versions of Perl Modules. I feel good about using Perl Modules that are updated. There is typically no problems. I think we should consider using the most current versions of Perl Modules. When you run the command 'perl Makefile.PL', it will warn you if there are any dependency modules not installed. This should be enough. I do; however, appreciate your comments Ken, and will wait until the community provides some input about my idea. -- Randy rmlscsi: [bogomips 1003.23] [GNU ld version 2.16.1] [gcc (GCC) 4.0.3] [GNU C Library stable release version 2.3.6] [Linux 2.6.14.3 i686] 19:32:00 up 6 days, 5:31, 1 user, load average: 0.20, 0.06, 0.02 -- http://linuxfromscratch.org/mailman/listinfo/blfs-dev FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
