Re: How to handle Cross-platform Perl, modules, and versioning

I would discourage that kind of test. Once you update the version of perl on Solaris, for example, you're screwed... I'd rather go for checking the version of perl.

Of course, the best thing would be a clean install. See my other post.

Comment on Re: How to handle Cross-platform Perl, modules, and versioning

Replies are listed 'Best First'.
Re: Re: How to handle Cross-platform Perl, modules, and versioning by BrowserUk (Patriarch) on Apr 15, 2003 at 22:50 UTC
Makes sense to me but i don't live in the world of running perl on 11 platforms, so I had to assume that the OP knows what he's doing in that regard. I'd amazed--and mighty impressed--if all the differences between those 11 platforms can be differenciated by either the OP's test or that of just the version. I know that perl is highly portable, but I was sure that the real test would probably be more complicated than the example the OP supplied, and I don't have the cross-systems experince to even guess what it would really look like. I read the OP's code somewhat differently to you--and I don't know which of us is closer--in as mach as I took the ".../Custom_mods..." to mean that each machine/platform had a standard install, but that they wanted to share their in-house modules from specific places. Maybe that makes sense in thier environment? Examine what is said, not who speaks. 1) When a distinguished but elderly scientist states that something is possible, he is almost certainly right. When he states that something is impossible, he is very probably wrong. 2) The only way of discovering the limits of the possible is to venture a little way past them into the impossible 3) Any sufficiently advanced technology is indistinguishable from magic. Arthur C. Clarke.	[reply] [d/l]
Re: Re: Re: How to handle Cross-platform Perl, modules, and versioning by P0w3rK!d (Pilgrim) on Apr 16, 2003 at 14:41 UTC
see node 248145 for more info	[reply]