Re^8: How do you distribute your Perl application to your customers?

Surely ("Don't call me Shirley") this is a great opportunity to show us what you have done and what doesn't work. I'm sure there are many pp users here who don't follow the mailing list. This forum has a well established history of providing solutions to problems :)

You keep saying things along the lines of 'trying very hard to use it [pp]' or 'struggle and don't know if I will succeed in time'. If you don't tell us the problems, we can't help fix them. Other methods of packaging apps have been provided. If you can't get them to work will you come back to tells us you are having problems with them, but not tell us the details of what happens, then ask for alternatives?

If as your posts suggest you are pushed for time, you are, IMHO, wasting time by not following the advice I've discussed.

Comment on Re^8: How do you distribute your Perl application to your customers? Download Code

Replies are listed 'Best First'.
Re^9: How do you distribute your Perl application to your customers? by kg (Acolyte) on Jan 13, 2010 at 10:27 UTC
I got your point and as I said I will do so in the future. I am not saying you won't be able to help me, I just wanted to know other possible solutions (thanks to you all! :-)) - that's all. In the meantime, a tireless user from the par mailing list actually solved the problem I had using pp. It was a problem with Digest's autoload functionality which collided with pp. par.pl calling `eval { $Digest::SHA::VERSION };` introduces the global variable `$Digest::SHA::VERSION` to `%{"Digest::SHA::"}` which causes Digest to skip `require Digest::SHA`. You get around this by adding `use Digest::SHA` to your code. Easy, once you know it. :-)	[reply] [d/l] [select]

Replies are listed 'Best First'.

Re^9: How do you distribute your Perl application to your customers?
by kg (Acolyte) on Jan 13, 2010 at 10:27 UTC

In the meantime, a tireless user from the par mailing list actually solved the problem I had using pp. It was a problem with Digest's autoload functionality which collided with pp.

par.pl calling eval { $Digest::SHA::VERSION }; introduces the global variable $Digest::SHA::VERSION to %{"Digest::SHA::"} which causes Digest to skip require Digest::SHA. You get around this by adding use Digest::SHA to your code. Easy, once you know it. :-)

[reply]
[d/l]
[select]