[Shipwright] Problems building newer packages

sunnavy sunnavy at bestpractical.com
Thu Oct 17 19:43:46 EDT 2013

Hi David

You can create them from META.yml of the package you want to import.
I made a simple script to do this, see attached, you can run it like

    perl /path/to/build-reqire-yml-from-meta.pl /path/to/META.yml /path/to/require.yml

then you can use "/path/to/require.yml" as the --require-yml argument.

-------------- next part --------------
A non-text attachment was scrubbed...
Name: build-reqire-yml-from-meta.pl
Type: text/x-perl-script
Size: 362 bytes
Desc: not available
URL: <http://lists.bestpractical.com/pipermail/shipwright/attachments/20131018/42335807/attachment.bin>
-------------- next part --------------


On Oct 18, 2013, at 5:20 AM, David Good <dgood at willingminds.com> wrote:

> Thanks!
> Is there a straightforward method for generating the YML files?  I'm
> adding back in the full list of modules for our distribution and have
> found another with the same problem (Class::Method::Modifiers) and
> suspect there may be others.  If it's fairly simple, I don't have a
> problem with doing it myself.
> On 10/17/2013 6:38 AM, sunnavy wrote:
>> Hi David
>> The reason is Test::Warnings uses Module::Build::Tiny as the build system,
>> which Shipwright doesn't handle right now.
>> I will update Shipwright for this soon, sorry for your inconvenience.
>> For now, I suggest you import Module::Build::Tiny and Test::Warnings
>> with specified --require-yml so Shipwright can skip the process of
>> running those packages' Build.PL when importing.
>> require ymls are attached.
> _______________________________________________
> Shipwright mailing list
> Shipwright at lists.bestpractical.com
> http://lists.bestpractical.com/cgi-bin/mailman/listinfo/shipwright

More information about the Shipwright mailing list