http://www.perlmonks.org?node_id=858816


in reply to Re: Packaging Perl Programs (is) Painful
in thread Packaging Perl Programs (is) Painful

mingw would be a welcome addition to AS ppm, if it installs as easily as you say. I am running 5.10 of ActiveState's installation, and its ppm is just awful. When you start it, it runs for two or three minutes in a single-threaded state that doesn't even yield to events, meaning that the window doesn't even redraw and can't be moved while it's busy.

I know ppm can handle multiple repositories; often that's the only way to get certain binary modules.

Maybe I should give it another try.

  • Comment on Re^2: Packaging Perl Programs (is) Painful

Replies are listed 'Best First'.
Re^3: Packaging Perl Programs (is) Painful
by Marshall (Canon) on Sep 03, 2010 at 23:01 UTC
    The mingw installation via ppm took about 3 minutes on the machine I'm using at the moment.

    A few comments about ppm:
    - First, yes it can take awhile for the gui to start and you do get the "hourglass phenomenon". During this time, it is re-syncing with the repositories that you have active. That means (a)if you've recently used it, it is a lot faster because your local info is more up to date, (b) the fewer repositories you have active, the less syncing it will have to do. For default I just leave the main AS one active and if I can't find what I want there, then I add more repositories as the hunt widens..

    - If the GUI offends you, then why use it? The command line I/F didn't go away. open an command window and type "ppm help" and you'll see what to do.

    Oh, an unrelated but perhaps nice point for you to know...the new version of PDK can do all of the "final polishing" of the .exe (embed your company's icon and put in the build version info, product name, etc) without having to fiddle with running another utility. It will have all the normal windows stuff.