in reply to Re^4: Bug in App::FatPacker?
in thread Bug in App::FatPacker?

You can use their perl as long as you don't use their makemaker since they patch makemaker to make packlists disappear , see Re^5: Module packlists vs. vendors

Replies are listed 'Best First'.
Re^6: Bug in App::FatPacker?
by elef (Friar) on Dec 06, 2012 at 11:26 UTC
    Thanks for the help.

    Now, I'm a bit out of my depth when it comes to remakeing modules. It would probably be simpler to generate these files or use a different linux distro for this purpose.

    Is there an easy way to generate a .packlist file? I gather that it's just a list of filenames.

    Alternatively, can you suggest a small linux distro that I could just drop in a VM or on a flash drive and get this done quickly?

      Ah, sorry for forgetting that MakeMaker problem---BrowserUK just helped me out of the same trap a while ago. The simplest thing to do is just to use some flavor of the cpan command to install your own MakeMaker, make sure your local path is in @INC before the /usr ones, and then reinstall everything your script needs. cpan then uses the untouched MakeMaker and installs the .packlist files correctly.

      Unfortunately there's no sane way to regenerate packlists after installation due to the way Perl allows you to freely use whatever namespace you like for your module. For example, Template::Parser is part of the Template Toolkit and should go into its packlist while Template::Timer is an external add-on that has its own packlist. There's no way to tell when you find the and files in the same directory. You could probably look at timestamps and stuff but it's bound to break at some point; much easier to just reinstall everything.