If it was just about not removing the files, that'd be easy, I solved that part in 15 minutes on Gentoo. Alas, the files are not even installed by a standard Makefile as produced by ExtUtils:MM when using the vendor_install target, so it doesn't seem only Debian's problem but intended behavior---with ExtUtils::MM being a core module I presume even some sort of official Perl policy. I'd be interested in why this is so and if I can/should circumvent it.
That is really hard to read/disgest.
I think you're wrong, I used make install_vendor and I got ../lib/perl5/MSWin32-x86-multi-thread/auto/Foo/.packlist
Sure, I used install_base , and my config is
$ perl -V:installvendor.* installvendorarch=''; installvendorbin=''; installvendorhtml1dir=''; installvendorhtml3dir=''; installvendorlib=''; installvendorman1dir=''; installvendorman3dir=''; installvendorscript='';
But that makes no difference
$ md tempjunk $ cd tempjunk $ h2xs -AX Foo Defaulting to backwards compatibility with perl 5.14.1 If you intend this module to be compatible with earlier perl versions, + please specify a minimum perl version with the -b option. Writing Foo/lib/Foo.pm Writing Foo/Makefile.PL Writing Foo/README Writing Foo/t/Foo.t Writing Foo/Changes Writing Foo/MANIFEST $ cd Foo $ perl Makefile.PL INSTALL_BASE=.. Checking if your kit is complete... Looks good Writing Makefile for Foo Writing MYMETA.yml and MYMETA.json $ dmake install_vendor cp lib/Foo.pm blib\lib\Foo.pm Installing ..\lib\perl5\Foo.pm Appending installation info to ..\lib\perl5\MSWin32-x86-multi-thread/p +erllocal.pod $ gtree -f -a .. .. |-- ../Foo | |-- ../Foo/Changes | |-- ../Foo/MANIFEST | |-- ../Foo/MYMETA.json | |-- ../Foo/MYMETA.yml | |-- ../Foo/Makefile | |-- ../Foo/Makefile.PL | |-- ../Foo/README | |-- ../Foo/blib | | |-- ../Foo/blib/arch | | | |-- ../Foo/blib/arch/.exists | | | `-- ../Foo/blib/arch/auto | | | `-- ../Foo/blib/arch/auto/Foo | | | `-- ../Foo/blib/arch/auto/Foo/.exists | | |-- ../Foo/blib/bin | | | `-- ../Foo/blib/bin/.exists | | |-- ../Foo/blib/lib | | | |-- ../Foo/blib/lib/.exists | | | |-- ../Foo/blib/lib/Foo.pm | | | `-- ../Foo/blib/lib/auto | | | `-- ../Foo/blib/lib/auto/Foo | | | `-- ../Foo/blib/lib/auto/Foo/.exists | | |-- ../Foo/blib/man1 | | | `-- ../Foo/blib/man1/.exists | | |-- ../Foo/blib/man3 | | | `-- ../Foo/blib/man3/.exists | | `-- ../Foo/blib/script | | `-- ../Foo/blib/script/.exists | |-- ../Foo/lib | | `-- ../Foo/lib/Foo.pm | |-- ../Foo/pm_to_blib | `-- ../Foo/t | `-- ../Foo/t/Foo.t `-- ../lib `-- ../lib/perl5 |-- ../lib/perl5/Foo.pm `-- ../lib/perl5/MSWin32-x86-multi-thread |-- ../lib/perl5/MSWin32-x86-multi-thread/auto | `-- ../lib/perl5/MSWin32-x86-multi-thread/auto/Foo | `-- ../lib/perl5/MSWin32-x86-multi-thread/auto/Foo +/.packlist `-- ../lib/perl5/MSWin32-x86-multi-thread/perllocal.pod 19 directories, 22 files
Ball is in your court.
In reply to Re^3: Module packlists vs. vendors
by Anonymous Monk
in thread Module packlists vs. vendors
by mbethke
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |