Got an unexpected "bank holiday", so I am playing.
Padre installs nicely on Debian Sid when using CPAN on 2010-05-24 ... I wonder if I am doing something wrong :P ... or maybe Padre is getting closer to being ready for prime-time.
Plugins that installed cleanly:
- Padre::Plugin::PAR
 - Padre::Plugin::XS
 - Padre::Plugin::Encrypt
 - Acme::Padre::PlayCode
 - Padre::Plugin::Nopaste
 - Padre::Plugin::DataWalker
 - Padre::Plugin::HTML
 - Padre::Plugin::HTMLExport
 - Padre::Plugin::JavaScript
 - Padre::Plugin::Kate
 - Padre::Plugin::CSS
 - Padre::Plugin::Ecliptic
 - Padre::Plugin::SpellCheck
 - Padre::Plugin::PHP
 - Padre::Plugin::ViewInBrowser
 - Padre::Plugin::PerlCritic
 - Padre::Plugin::Debugger
 - Padre::Plugin::Encode
 - Padre::Plugin::Alarm
 - Padre::Plugin::Swarm
 - Padre::Plugin::ClassSniff
 
Plugins that fail tests:
- Padre::Plugin::Shell::Base
 - Padre::Plugin::CommandLine
 - Padre::Plugin::InstallPARDist
 - Padre::Plugin::Vi
 - Padre::Plugin::Template
 - Padre::Plugin::Filter
 
Some plugins are still using the old API, I guess. Did you try Padre::Plugin::Catalyst?
ReplyDeletePadre::Plugin::Catalyst and Padre::Plugin::XML also pass all tests.
ReplyDelete