Beefy Boxes and Bandwidth Generously Provided by pair Networks
Just another Perl shrine

Comment on

( #3333=superdoc: print w/replies, xml ) Need Help??

I have a problem understanding the proper use of .packlist files in a vendor install:

Recently I tried packing a script and its dependencies for distribution using App::FatPacker. It failed due to missing .packlist files for pretty much everything. The man page says:

Unfortunately most vendors strip the .packlist files so if you installed modules via e.g. apt-get you may be missing those modules; installing your dependencies into a local::lib first is the preferred workaround.
Now I do like my Perl stuff to be installed via a package manager so that local::lib suggestion sounds like an unnecessary PITA. Also, I use Gentoo Linux at home so the missing packlists should be easy to fix, right? Well, after quickly disabling the part of Gentoo's ebuild process where it deletes all packlists, I found that didn't quite do the trick as the deleting is just a "safety net", they're usually not installed by the install_vendor target in module makefiles anyway.

Now my question is, is there a compelling reason to do it this way and break all kinds of useful tools that need Module::Installed and the like, or just a concession to vendors that complained about the couple hundred bytes and one inode per module that the packlists take up? The Debian guys state that

Those files are useless, and (in some cases) have the additional problem of creating an architecture-specific directory name in an architecture-independent package. (from lintian via)
... the first part of which is obviously false, and the second one may be relevant iff you share some installation between machines of different architectures, but certainly not to the vast majority of users. Any other reason? And/or, is there a way to get around it without giving up the vendor vs. site installation distinction?

In reply to Module packlists vs. vendors by mbethke

Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post; it's "PerlMonks-approved HTML":

  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.
  • Log In?

    What's my password?
    Create A New User
    and all is quiet...

    How do I use this? | Other CB clients
    Other Users?
    Others cooling their heels in the Monastery: (4)
    As of 2018-03-20 08:19 GMT
    Find Nodes?
      Voting Booth?
      When I think of a mole I think of:

      Results (248 votes). Check out past polls.