perl 5.10.1 is out, so i just built it for mandriva cooker - after fighting the build system which seems to be broken very often those days. :-(
it's currently propagating on mirrors, and should hit your machines soon... lots of other packages will need to be rebuilt, so you may want to run urpmi with the --keep flag.
in other news, parrot 1.5.0 is also available on cooker since yesterday.
2009-08-24
2009-08-22
new pandemic release
games::pandemic 0.7.0 is now on cpan, with a lot of improvements and a crash fix:
- wiping all cubes from a city if a cure has been found for the disease
- reacting to winning conditions
- reacting to game over condition when no more disease cubes
- possibility to see cards already played / discarded
- possibility to see past infections
2009-08-17
more dzil goodness
i'm happy to announce yet another plugin for dist-zilla: critictests.
in your dist.ini, just add:
of course, since your code will be munged by dist-zilla, code that passes critics in your repo may fail after being rewritten... case in point: stricture use, since dist-zilla-plugin-pkgversion will insert a version just after the package statement - and thus before any use statements. in order to make your code compliant again, just move the use strict / warnings before the package. indeed, use is lexically scoped, and thus the scope of the use statement will be the whole file.
your code will now look like:
in your dist.ini, just add:
and dist-zilla will automatically create for you an xt/author/critic.t file that will criticize your code during author tests.[CriticTests]
of course, since your code will be munged by dist-zilla, code that passes critics in your repo may fail after being rewritten... case in point: stricture use, since dist-zilla-plugin-pkgversion will insert a version just after the package statement - and thus before any use statements. in order to make your code compliant again, just move the use strict / warnings before the package. indeed, use is lexically scoped, and thus the scope of the use statement will be the whole file.
your code will now look like:
and of course, perlcritic this time will now be happy.use strict;
use warnings;
package Foo::Bar;
2009-08-09
perl 5.10.1-rc1 available on mandriva
perl 5.10.1-rc1 has been released 3 days ago, so i packaged it for mandriva. the good thing is that a lot of patches that we were adding to our perl are now merged upstream.
the new perl (perl-5.10.1-0.rc1.2mdv at the time of writing) rpms are available in mandriva testing media. you can install them with:
the new perl (perl-5.10.1-0.rc1.2mdv at the time of writing) rpms are available in mandriva testing media. you can install them with:
please report any problem to either mandriva cooker mailing list, or to perl 5 porters if that's a perl related bug.# urpmi perl perl-base --media "Main Testing"
2009-08-08
epidemics strike in games::pandemic!
games::pandemic 0.6.0 is now on cpan, with a lot of improvements:
- introducing epidemic events - fear! :-)
- closing current game is now supported
- player cards now displayed in a window of their own
- detecting game over condition when no more cards
- sorting cards by type then by disease then by city name
- introducing a new "action" menu, with shortcuts for actions
- actions now independant of buttons / menu for easier reuse
2009-08-07
shipping compile tests with dist-zilla
perl community places some emphasis on testing. which is great, since it enhances the overall quality of perl ecosystem.
the first, easiest test that one should provide is basic: making sure the modules compile. we have 2 options here:
the first, easiest test that one should provide is basic: making sure the modules compile. we have 2 options here:
- either create a test and add some use_ok('Foo::Bar'). but we then need to update it whenever we add more modules to our distribution - without forgetting to update test count.
- or, to get rid of this burden, ship a test that automatically finds the module and tries to compile them.
and you will get a brand new t/00-compile.t that will test your modules and your scripts one by one. this my take some time if your dist ships a lot of modules having lots of prereqs, especially if they are a bit slow to compile such as Moose. but this will potentially find more compile errors in your modules.[CompileTests]
2009-08-06
more moose support in dzp:autoprereq
dist::zilla::plugin::autoprereq just gained more moose support: it can now extract the base module declared with:
it's not perfect since it only extracts the first base class, but i think it will cover 90+% of the cases out there.extends 'Foo::Bar';
Subscribe to:
Posts (Atom)