>> My concept for Alien::Base is to never \emph{install} to system. If library
>> is installed in system, then use it. If not then install to a
>> File::ShareDir location.

On Fri, Jan 20, 2012 at 9:49 AM, Chris Marshall <[email protected]> wrote:
> The needed library may be already installed
> on the system.  I don't think Alien::XXX should
> re-install XXX in another location as that might
> cause surprising breakage and path problems.

A File::ShareDir install would be totally independent of anything
already installed, and it is in the Perl directories which is what is
expected when one installs a Perl module. I know that the optimal
would be to install system-wide, but I kept finding edge cases, and
use cases that I didn't want to handle. Perhaps this all can be added
later.

I figured if an Alien:: module is installed it is most likely for a
Perl module dep. Therefore as long as I can make the Perl module happy
then other tools exist to install for the system.

\begin{rant}
Actually it really irks me that there is no good way to hook into apt
(i know that this is a linux-only arg) but grrr, its a Perl-based
system. If only you could invoke it a get some useful info. Even the
apt-cache search results are tremendously hard to get to work in all
cases.
\end{rant}

Which libraries need root priv when outside system folders? Some HW
drivers, anything else?

Joel

_______________________________________________
Perldl mailing list
[email protected]
http://mailman.jach.hawaii.edu/mailman/listinfo/perldl

Reply via email to