Dump fixtures from source database to filesystem then import to
another database (with same schema) at any time. Use as a constant
dataset for running tests against or for populating development
databases when impractical to use production clones. Describe fixture
set using relations and conditions based on your DBIx::Class schema.
WWW: https://metacpan.org/release/DBIx-Class-Fixtures

Remove all := from BUILD_DEPENDS, here are never needed.
While there, cleanup, and sort depends.
When build and run dependencies are the same, there are three ways to
avoid duplicating the list while not adding the framework added
BUILD_DEPENDS to the RUN_DEPENDS. In order of preference, they are:
1) use RUN_DEPENDS to set BUILD_DEPENDS:
BUILD_DEPENDS= ${RUN_DEPENDS}
RUN_DEPENDS= foo:bar/baz
2) create another variable and use it:
MY_DEPENDS= foo:bar/baz
BUILD_DEPENDS= ${MY_DEPENDS}
RUN_DEPENDS= ${MY_DEPENDS}
3) use BUILD_DEPENDS to set RUN_DEPENDS and force evaluation:
BUILD_DEPENDS= foo:bar/baz
RUN_DEPENDS:= ${BUILD_DEPENDS}
Sponsored by: Absolight

Change the way Perl modules are installed, update the default Perl to 5.18.
Before, we had:
site_perl : lib/perl5/site_perl/5.18
site_perl/perl_arch : lib/perl5/site_perl/5.18/mach
perl_man3 : lib/perl5/5.18/man/man3
Now we have:
site_perl : lib/perl5/site_perl
site_arch : lib/perl5/site_perl/mach/5.18
perl_man3 : lib/perl5/site_perl/man/man3
Modules without any .so will be installed at the same place regardless of the

Dump fixtures from source database to filesystem then import to
another database (with same schema) at any time. Use as a constant
dataset for running tests against or for populating development
databases when impractical to use production clones. Describe fixture
set using relations and conditions based on your DBIx::Class schema.
WWW: http://search.cpan.org/dist/DBIx-Class-Fixtures/