As some of you will have noticed,
some Padre::Plugin::... don't work any more with current releases of Padre.
As Padre::Plugin requires the Plugin to have a valid version of the form:
our $VERSION = '0.01'; or our $VERSION = '0.101';
Which is ok if you are using Module::Install but not so if you chose to
develop using Module::Build or Dist::Zilla.
So we now have working Plugins in trunk (svn) which fail to load using
perl dev -a.
So here is my suggestion.
We add a plugin_version method to Padre::Plugin
sub Padre::Plugin {
return (
'version' => '0.91',
);
}
where version, could be either
a, the built against version of Padre trunk, which will always be odd.
b, left to the developers choice, just like Padre api numbers.
Then we have a compromise, every will plugin now has a version, plugin
can use which ever module build there developer wishes to use and the
really BIG plus perl dev -a will work enabling plugins to be developed
against trunk.
I can't wait for the critiques ;)
regards
bowtie
_______________________________________________
Padre-dev mailing list
[email protected]
http://mail.perlide.org/mailman/listinfo/padre-dev
