Hard to believe it’s already the middle of August..and the end of the official summer months. How do I make myself feel better about the inevitable change in seasons? Well, I curl up on my chaise lounge and read a success story about another happy ActiveState customer. This time it’s Alterpoint – and you can read the full story here. And when you’re finished reading – get out and enjoy that sun!
-
Recent Posts
Categories
Archives
- October 2009
- September 2009
- August 2009
- July 2009
- June 2009
- May 2009
- April 2009
- March 2009
- February 2009
- January 2009
- December 2008
- November 2008
- October 2008
- September 2008
- August 2008
- July 2008
- June 2008
- May 2008
- April 2008
- March 2008
- February 2008
- January 2008
- December 2007
- November 2007
- October 2007
- September 2007
- July 2007
- May 2007
- April 2007
- January 2007
- December 2006
- November 2006
- October 2006
- September 2006
- July 2006
- June 2006
- May 2006
- April 2006
- March 2006
- February 2006
- January 2006
- December 2005
- November 2005
- October 2005
- September 2005
- August 2005
- July 2005
The success story is very misleading."ActiveState continually monitors and tests all updates to ensure that ActivePerl is always using the latest and most secure Perl release."
Well something as basic and as critical as the cpan shell doesn't work. The latest version "ActivePerl-5.10.0.1003-MSWin32-x86-285500.msi" should never have been released until this was problem was resolved.
The responding comment seems tangential to the quote it takes out of context. That ActivePerl uses the latest and most secure Perl is not contradicted by your point. Indeed, AP 1003 went out with the cpan shell functionality broken. This was due to a bug in the YAML module (not the core) with a simple fix posted at http://perlmonks.com/?node_id=706074. This has been resolved for the AP 1004 release (due soon).