Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss
ActiveState's PPM distropref patch of Win32::API
4 views
Skip to first unread message
bulk 88
Oct 19, 2012, 8:25:19 PM10/19/12
to ja...@activestate.com, libw...@perl.org
ActiveState has been patching Win32::API since API 0.58 to today (with patch http://ppm4.activestate.com/MSWin32-x86/5.10/1000/C/CO/COSIMO/Win32-API-0.58.d/log-20090527T160936.txt no patch http://ppm4.activestate.com/MSWin32-x86/5.10/1000/C/CO/COSIMO/Win32-API-0.57.d/log-20081017T081820.txt ) so the Win32::API::Callback tests are skipped since they used to crash on 90% of compilers. Since API 0.65 the patch has failed (see http://ppm4.activestate.com/MSWin32-x86/5.14/1400/C/CO/COSIMO/Win32-API-0.65.d/log-20120213T025817.txt ) to apply because of a code formater being run on Win32::API between 0.64 and 0.65 in this commit https://github.com/cosimo/perl5-win32-api/commit/ebbafaffc6b2c895c7a73bfa8d6e0ce97ec2a39a#L2L55 . Can something please be done by ActiveState to stop the PPM build farm from trying to patch Win32::API?
Jan Dubois
Oct 26, 2012, 7:40:30 PM10/26/12
to bulk 88, libw...@perl.org
I've removed the Win32-API distroprefs from the PPM build system and
pushed the change to all Windows builders. I've then forced a rebuild
of the latest Win32-API (0.73), and the builds all succeeded without
problems. So the vestigial traces in the files to keep the patch
working can now be removed.
Cheers,
-Jan
pushed the change to all Windows builders. I've then forced a rebuild
of the latest Win32-API (0.73), and the builds all succeeded without
problems. So the vestigial traces in the files to keep the patch
working can now be removed.
Cheers,
-Jan
0 new messages