Randy McMurchy wrote: > 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.
I do keep the versions of perl modules in the book on anduin, but I don't know if they are actually used much. Personally, I just use the cpan method and it downloads, compiles, and installs with one line, dependencies included. I still consider it a source build and the code is stored in /root/.cpan/sources. -- Bruce -- http://linuxfromscratch.org/mailman/listinfo/blfs-dev FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
