Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss
MYMETA Files Not Getting Packed
3 views
Skip to first unread message
John M. Gamble
Sep 6, 2012, 5:12:26 PM9/6/12
to Module Build
Are MYMETA.yml and MYMETA.json not meant to be part of a perl package? I
admit to adding them to the MANIFEST without considering it. What I found
more interesting is that the MYMETA files were not included in the
package.
I'm assuming this is an out-right error -- even if the MYMETA files are
unnecessary, their presence in the MANIFEST file should at least merit a
warning, right?
Thanks,
-john
admit to adding them to the MANIFEST without considering it. What I found
more interesting is that the MYMETA files were not included in the
package.
I'm assuming this is an out-right error -- even if the MYMETA files are
unnecessary, their presence in the MANIFEST file should at least merit a
warning, right?
Thanks,
-john
Leon Timmermans
Sep 6, 2012, 5:15:58 PM9/6/12
to John M. Gamble, Module Build
On Thu, Sep 6, 2012 at 11:12 PM, John M. Gamble <jga...@ripco.com> wrote:
> Are MYMETA.yml and MYMETA.json not meant to be part of a perl package? I
> admit to adding them to the MANIFEST without considering it. What I found
> more interesting is that the MYMETA files were not included in the
> package.
This is very much deliberate. MYMETA *must* be generated during the
> Are MYMETA.yml and MYMETA.json not meant to be part of a perl package? I
> admit to adding them to the MANIFEST without considering it. What I found
> more interesting is that the MYMETA files were not included in the
> package.
«perl Build.PL» phase. Adding them to the distribution is at best
useless, and at worst actively harmful.
> I'm assuming this is an out-right error -- even if the MYMETA files are
> unnecessary, their presence in the MANIFEST file should at least merit a
> warning, right?
Module::Build, though.
Leon
0 new messages