On 2/5/06, Tyler MacDonald wrote: > > ActiveState always serves the last available version where all tests > passed on a given platform. It attempts to build and test every package on > CPAN at least once a week. If something isn't available, it means the tests > failed, which could mean: >
Just an example, IO::All [1] version 0.33 has been available since Dec 17, 2004. It passed testing many times, at least according to its testers page [2]. My default 5.8.7 ActivePerl distribution lists IO::All version 0.17 . I'm not sure which of the reasons you listed are valid, as a user I have no real way of knowing... that's why I thought an automated Windows-PPM sub-domain on CPAN which would be updated automatically for every new package would be great. What you are saying, that ActiveState already have such a system, is news to me, especially in view of examples such as the above... I would rather use CPAN, but the PPM works fine for me, only it's not as updated as CPAN. [1] http://search.cpan.org/dist/IO-All/ [2] http://testers.cpan.org/show/IO-All.html#IO-All-0.33 > > Phillipe Chaisson aka "Gozer" (one of the mod_perl authors) is > responsible for the ActiveState PPM repositories now, Hi Gozer, nice to meet you. Gratz on ActiveState's move to a new company, good luck :) > and the he's told me > that if there's an issue with the build system that causes some particular > module's build to fail when it shouldn't, he'll fix it right away if it can > be identified. http://ppm.activestate.com/ contains full logs of every > single package build success and failure, so if a package isn't available, > have a look there and see why/how it failed and let him know. > > Cheers, > Tyler > Cool! Didn't know about the http://ppm.activestate.com/ . Looking at the IO-All package, I see it failed because of the prereq Spiffy. Looking at Spiffy, it failed because of Scalar-List-Util [3]. Which is funny because it turns out to be a problem for other people, who mentioned it in other replies to this thread... :) [3] http://ppm.activestate.com/BuildStatus/5.8-windows/windows-5.8/Scalar-List-Util-1.15.txt I'd like to clarify something - I don't really expect Gozer to handle this problem... or a problem with any other module... there are so many, how can a single person keep up? It would be better if the system were automated... and worked :) BTW Gozer have you looked at the first line: Cannot forceunlink D:\cpanrun\build\5-8-0\lib\auto\List\Util\Util.dll: Permission denied at D:\cpanrun\build\5-8-0\lib/File/Find.pm line 874 Maybe the script is trying to delete a file that the system thinks is in use? Or something similiar? Windows has that annoying habit of refusing to delete things it thinks are in use... Moin Tels, Regarding what you said, of course the problem is with non pure-Perl modules. For pure-Perl ones, I can use CPAN... and yes, I'm only talking about Windows. Forgot there was PPM for other archs until you reminded me :) I would rather not use 2 seperate package installation schemes... either CPAN or PPM (or something else), not both. As for the problem of different DLLs etc., I don't think any of Blizzard's 5.5 million customers have ever had a problem installing WoW because they were missing a DLL from some Office version... Just to give an example... why should a PPM package be any different? Yes, I'm a noob when it comes to these things, sorry :) Cheers, -- Offer Kaye
