in reply to Bundling perl modules with a larger system

So, erm, have you heard of par? :)

Update: Bah, mislink. See two nodes down please . . .

The cake is a lie.
The cake is a lie.
The cake is a lie.

  • Comment on Re: Bundling perl modules with a larger system

Replies are listed 'Best First'.
Re: par
by mattsheppard (Acolyte) on Dec 20, 2007 at 02:50 UTC

    No, can't say I had - Looks like a way of bundling a bunch of files into a single perl script, which unpacks itself (like a self extracting archive), yes?

    Actually unpacking the files onto the file system isn't a big issue for me, I guess I'm more concerned with finding an easy way to work out (and ideally build) the files which need packing.

    Maybe an example...

    Say I want to ship Archive::Zip along with my app. From the readme I find that it requires Compress::Zlib, which then appears to require the IO::Compress::Gzip, IO::Uncompress::Gunzip, Compress::Raw::Zlib and so on.

    What I'd like, is a way to build all the dependencies in one hit, so I can bundle up the result, but I'm worried that just using MCPAN with something like PREFIX=/tmp/matts_new_build_area would skip Compress::Raw::Zlib if that happened to be installed locally on the box.

    Hopefully that makes the issue I'm running into a little clearer.

    Thanks, Matt Sheppard

      GRAH, sorry that was a bad link. I plead head cold . . .

      I mean PAR (and http://par.perl.org/) which is a different beast altogether. That lets you package a script and requisite modules into a single executable archive.

      The cake is a lie.
      The cake is a lie.
      The cake is a lie.

        Ahhhh, that does look promising.

        No doubt it will take me some time to investigate fully, but many thanks for the pointer!

        Matt

      Have a look at cpandeps


      holli, /regexed monk/