On Monday 10 November 2014 17:02:28 Tor Arntsen wrote: > IPC::Run is not part of the AIX perl core, unfortunately.
I see, ftp://public.dhe.ibm.com/aix/freeSoftware/aixtoolbox/SPECS/perl-5.6.1-4.spec > Anything installed for a libcurl build really has to be part of what's > maintained through the package manager, in other words - no downloaded > file(s) (including via cpan). It's not just about being able to > quickly add another build system (for autobuilds or otherwise), for > example, one of our customers occasionally builds the libcurl RPM (for > AIX) themselves (normally we provide one for them). But on their build > system everything installed must be through the package management > system. They cannot (and I would not myself either) depend on > something installed sidewise. It quickly gets out of hand when this is > a system installed by an organisation instead of just a single > computer owned by a single developer. > > In general I wish that the testing environment (and everything else) > depends on as little complexity as possible, i.e. standard shell (and > not depending on bash'isms, for example), sed, awk etc. These days a > basic Perl system is part of nearly every *nix system out there, and > Windows as well. But just the core. IPC::Run already exists and solves the problem. Can you even consider installing this single module? Otherwise it has to be replaced by plain ol' fork/exec/open/dup/..., introducing bugs that might have been solved in IPC::Run a few yers ago. Now this is actually more "complex" than pulling the module from CPAN. I do not know where your customer gets their packages from, but they could try to request their distributor for inclusion of IPC::Run. Would that be possible? -- Kind regards, Peter https://lekensteyn.nl ------------------------------------------------------------------- List admin: http://cool.haxx.se/list/listinfo/curl-library Etiquette: http://curl.haxx.se/mail/etiquette.html
