On Sun, May 31, 2015 at 3:42 PM Zakariyya Mughal <zaki.mug...@gmail.com> wrote:
> On 2015-05-31 at 16:35:33 -0400, Chris Marshall wrote: > > One problem I've had with Alien installs is control of the install > process. > > > > In most cases, as a PDL user I *don't* want unknown > > build-test-install processes to take place without my concurrence. > > I would far prefer a LibDetect::XXX first with an option of > > Alien::XXX install after that. > > > > Another thing that would be reassuring to me is the ability to > > find/view/remove any and all files installed by Alien::XXX. > > > > Just some things I've been bitten by with the original Alien approach... > > Yes, I would first go with extending the current system library > detection in the builds and just adding an additional probe to check if > the appropriate Alien package is installed after the system check. > > Moving that towards an (optional) automatic Alien::* build dep can be > looked at later. > > Alien::Base based Alien:: modules of course DO check for the library installed system-wide before installing it in a per-perl (even per-local-lib) path. When it is found in the system, the installed and used Alien:: module is only a shim. [snip] Joel
------------------------------------------------------------------------------
_______________________________________________ pdl-devel mailing list pdl-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/pdl-devel
