On Tue, Dec 11, 2012 at 06:47:25PM -0600, 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. > > Thoughts? > Sounds nice, but what about when a newer version of a module suddenly brings in a whole load of extra dependencies ? I'm thinking of libwww-perl : the book is on 6.04, I've stuck to 5.837 because when I tried 6.02 it appeared to need a shed-load of additional dependencies.
I gave up when 6.02 reported that Encode::Locale wasn't found (probably a warning) along with File::Listing HTTP::Cookies HTTP::Daemon HTTP::Date HTTP::Negotiate HTTP::Request HTTP::Request:;Common HTTP::Response HTTP::Status LWP::MediaTypes Net::HTTP WWW::RobotRules (which all gave me the impression that they really were required). But I see from a fairly recent version of the book that 6.04 apparently needs none of these, so perhaps there is nothing to worry about. I'm also slightly dubious about "download the current version" because one of the packages I rely on [ Image::ExifTool ] has versions marked as 'stable', which get uploaded to CPAN, and intermediate development versions. If every download page points to a stable version, or at least gives the information somewhere on the page, that isn't a problem, but I'm not sure if all CPAN devs follow that sort of model. ĸen -- das eine Mal als Tragödie, das andere Mal als Farce -- http://linuxfromscratch.org/mailman/listinfo/blfs-dev FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
