in reply to Re^3: ExtUtils::MakeMaker and dot files
in thread ExtUtils::MakeMaker and dot files

Folks, I already covered this and I don't know how else to say it: my MANIFEST.SKIP file does indeed exist; it skips .AppleDouble folders; and the MANIFEST file itself does not contain .AppleDouble folders or files. THIS IS ALREADY IN EFFECT.

And yet my make will still grab lib/Project/.AppleDouble/Foo.pm, even though the MANIFEST *only* says lib/Project/Foo.pm.

For example:


$ make
...
cp lib/Project/Foo.pm blib/lib/Project/Foo.pm
cp lib/Project/.AppleDouble/Foo.pm blib/lib/Project/.AppleDouble/Foo.p
+m
...

$ cat MANIFEST
...
lib/Project/Foo.pm
...

[download]

The MANIFEST did not call for the files in the .AppleDouble folder, but they are still copied to blib. This is still a problem.

Replies are listed 'Best First'.
Re^5: ExtUtils::MakeMaker and dot files
by Anonymous Monk on Jul 20, 2012 at 00:59 UTC

    The MANIFEST did not call for the files in the .AppleDouble folder, but they are still copied to blib. This is still a problem.

    Well, .AppleDouble/Foo.pm sure did not get copied to blib (I tested)

    But lib/.AppleDouble/Foop.pm did -- you should have been more specific!

    But I'd say its still not a problem because the purpose of MANIFEST.SKIP is to control which files get put into a tarball when you use make dist -- and if you do use  make dist then the resulting tarball will be free of .AppleDouble folders

    Otherwise you'd have to use the icky PM_FILTER option, or the laborious PM option 

        PM => {
        'Foo.pm'      => '$(INST_LIBDIR)/Foo.pm',
        'lib/Foop.pm' => '$(INST_LIBDIR)/Foop.pm',
    },

    [download]
[reply]
[d/l]
[select]

      Sigh. But we aren't making tar balls for distribution in this case. We are moving library-type code to a common location on a server to run in a dev environment. When I run my make mantra, the resulting Makefile itself has TO_INST_PM = lib/Project/.AppleDouble/Foo.pm in it. That is 100% my problem and it doesn't relate in any way to MANIFEST. I keep saying that MANIFEST isn't my problem, and yet it keeps coming up. What words am I not saying to make this clear?

      My solution has to reside in keeping Makefile.PL from recursing into .AppleDouble directories inside of lib. Or I need a completely different tool or approach. MANIFEST would only be relevant if I could have make install read the MANIFEST when moving to the perl lib area.

      BTW, I tried PM_FILTER => "grep -v \'.AppleDouble\'",, but that didn't seem to do anything--I may just not quite gotten the sytax or quoting quite right?

      I also looked into hacking out the .AppleDouble lines from the Makefile itself, but since I don't quite know what's going inside there, maybe that's a bad idea.

[reply]
[d/l]
[select]

        The AppleDouble folders exist because of the afp connection that I am making to access the files. I can side step this (we hope) by using SFTP instead. This wont write AppleDouble any more and I should be all set.

[reply]

        BTW, I tried PM_FILTER ...

        But have you read the the docs for PM_FILTER?

[reply]

In Section Seekers of Perl Wisdom