Hi all, I've been working on updating the Perl Modules page. I really like how all the dependency links now point at a page where you can download the current version of the package instead of hard-coding a version into the BLFS instructions.
This makes the upkeep of the Perl Modules page much more simple. I cannot see a reason why we do not point all Perl Modules to a development page where you can download it. This would make a zero maintenance environment for the Perl Modules from an editor standpoint. There really is no reason to hard code version numbers into the BLFS Perl Module instructions any longer now that individual pages exist on CPAN for each module. I would like to get rid of hard-coding version numbers for *all* Perl modules. It would be an easy task to do this. And then the BLFS editor staff never has to worry about updating the page or keeping links on Anduin current. It seems win-win to me. Thoughts? -- 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] 18:36:00 up 6 days, 4:35, 1 user, load average: 0.19, 0.05, 0.01 -- http://linuxfromscratch.org/mailman/listinfo/blfs-dev FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
