Re: Module compilation hell

The question, or possibly solution, here, seems to be 'why dont we have binary repositories for CPAN modules?' There are plenty of Windows/PPM ones, why not for various unix/linus distributions as well?

At work we also try not to overuse perl modules either. I assume the reason is to spare the customer support people (who also install stuff), from jumping through too many hoops to get things working.

Having said that, we tend to cheat anyway. Our software is installed on HP-UX and AIX machines. These are luckily standard enough that we just provide a bunch of pre-compiled modules, and it *just works*. We even provide an entire perl install complete with modules for machines where perl 5 hasnt been installed (HP-UX comes with perl 4), and that also *just works*.

So, once you get the things installed, why make your customers go through it all again? Pack up a standard lib directory and give it to them.

Comment on Re: Module compilation hell

Replies are listed 'Best First'.
Re: Re: Module compilation hell by hardburn (Abbot) on Mar 31, 2004 at 14:30 UTC
There are plenty of Windows/PPM ones, why not for various unix/linus distributions as well? The simpile answer is that most Windows installations don't have a compiler easily available, and most nix boxes do. If you want a binary package on a nix system, you should probably look up whatever package manager your system provides (RPM, DEB, whatever). ---- `: () { :\|:& };:` Note: All code is untested, unless otherwise stated	[reply] [d/l]
Re: Re: Module compilation hell by mpeppler (Vicar) on Mar 31, 2004 at 15:41 UTC
In the case of the Sybase modules - the binaries depend too much on the type and version of the local Sybase installation, not to mention the various flavors of perl, etc. Maintaining all of these binaries is time-consuming, and difficult. I've been tempted to do it, but each time I look at the problem I find that it creates more problems than it solves. Michael	[reply]