On Tue Oct 19 15:50:18 2010, DHORNE wrote:
Show quoted text> Hi
>
> This module performs a simple task simply. I'm not really keen to add
> much bloat to it. In
> my environments, I have a simple Perl script for releasing code,
> including running DDL
> upgrades. It updates the source from subversion before deploying the
> code. This is done
> outside of DBIx::VersionedDDL and works well for me.
That is an approach that makes perfect sense. Maybe I'll also do just
some script to get the files before running DBIx::VersionedDDL.
I'm just trying to think of unified interface/tool to push ddl updates
in many different locations.
Show quoted text>
> Having said that, if you can think of a simple way to add a plugin
> capability without
> breaking the existing API or adding significant complexity, then I
> will most likely be more
> than happy to add it. RT #61592 contains a proposal to add callback
> functionality, but I
> never heard back from the OP. Perhaps you could come up with an
> approach together.
My, still somewhat vague, idea was to have a subclass with an interface
of say 'list_files', 'get_file', 'store_file'.
It could then load plugins via say MooseX::Object::Pluggable.