[mh] MisterHouse strategy for @INC and provided libs

[Lieven H. <li...@li...>]

Hello list,

I'm in the process of upgrading my MisterHouse server to the latest OS for my computer. In the process I encounter the following problem: I installed a relatively recent Perl version on the account that runs MisterHouse. Apparently MisterHouse somewhere internally overwrites the default @INC module include path that is active when MisterHouse is launched. I still need to figure out where this is done and I'm trying to understand why this is done. It seems that instead of searching for installed modules in my local library path MisterHouse tries to find certain (but not all?) modules in the system lib (where they are not available since I don't want to mess with the system Perl). Moreover, I don't think this is how an application should behave, but this is just IMHO.

I've documented it here: https://github.com/hollie/misterhouse/issues/247

Because I encountered this problem I started wondering: why are we not using CPAN to install required modules instead of providing our 'own' (old?) versions of default modules with the MisterHouse application? Keeping those up to date in our own archive seems bothersome to me and not really productive/useful?

Did we have experiences in the past that caused us to move away from CPAN? What is the reasoning behind this way of working?

Kind regards,
 Lieven.