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

I didn't need any non-core modules, but if I had, and gotten permission to distribute them, it would have trivial to put them in them somewhere in the tarball. (tarball we distributed then was several hundreds of Mb large, far larger than a perl distro at that time).

There wasn't much enjoyment though - it was just work.

Comment on Re^3: How do you distribute your Perl application to your customers?

Replies are listed 'Best First'.
Re^4: How do you distribute your Perl application to your customers? by kg (Acolyte) on Jan 12, 2010 at 07:46 UTC
Sorry, I tried to be ironic - I think it is hard work - and must have been much more when you worked on it. How did you scan the dependencies?	[reply]
Re^5: How do you distribute your Perl application to your customers? by JavaFan (Canon) on Jan 12, 2010 at 10:51 UTC
Considering I wrote the Perl programs, there wasn't any need for any scanning of dependencies. Now that I think of it, there was a non-core module that we used: sybperl (Sybase bindings to Perl). I used sybperl instead of DBI because sybperl gives you many of the calls that are available on the C-level as well, which means 1 meter of dead-tree documentation¹ (far, far more than DBI/DBD::Sybase), more features, and the ability to quickly prototype (or mimic) something that would later (or was already) written in C or C++ -- the main development languages in the company I then worked for. ¹Sybase has (had? I haven't used Sybase for a decade) all its documentation also available online: it keeps (kept?) all its documentation in SGML format, using that as input for both its books and its website.	[reply]