On Fri, Sep 10, 2010 at 5:53 AM, Chris Marshall <[email protected]> wrote:
> In another thread, the recommendation to build > perl modules (e.g., PDL) *not* using the system > perl came up again. > > My experience is that for maximum portability > and testability you usually want to build > against the "official OS perl" in the > "official OS location". That way other users > and developers can reproduce your build > environment which is needed to diagnose and > fix bugs. > > The point is that if you need to be root to install the module then you probably don't want to do it. There are some modules that try to install over the top of the vendor modules and that can't be a good thing. The safe way is to set PREFIX when you build your module so that it installs into a location that you control. Once you start building modules from CPAN and installing them into the normal system tree you might get problems with vendor supplied RPM versions of the same module (which might be a different version and which therefore might break your code or your module you installed over the top might break a system program). Maybe all these problems associated with mixing user modules with vendor RPM modules have been fixed now. Installing perl is so trivial that it never crosses my mind to use the system perl any more. I got burnt too many times (and a lot of times the system perl is far older than current perl which gets annoying quickly). Tim
_______________________________________________ Perldl mailing list [email protected] http://mailman.jach.hawaii.edu/mailman/listinfo/perldl
