From: Lieven H. <li...@li...> - 2013-08-19 06:54:21
|
Hey RJ, Op 19-aug.-2013, om 03:54 heeft RJ Clay <ja...@rj...> het volgende geschreven: > On Sun, 2013-08-18 at 15:46 +0200, Lieven Hollevoet wrote: > >> Op 17-aug.-2013, om 14:07 heeft John <jo...@to...> het volgende geschreven: >> >>> >>> The advantage would be that it would take more effort to test/update MH >>> core code as each of its dependent 3rd party modules changes (new >>> versions released). This includes making sure the MH core works with >>> multiple versions of the same dependent module simultaneously. >>> >>> The way it is currently we can set it and forget it. We would only >>> utilize a new dependent module when MH requires something in that new >>> version. >> >> That is one way of looking at it. On the other hand we're missing out >> all bug fixes that are applied to the modules we use too, because I >> don't believe somebody is monitoring the modules used by MisterHouse >> to see if it gets time to update the version that is delivered with >> the MisterHouse package. > > That's something I was thinking as well. > > Note that I'm already, in effect, testing MH with 'current' versions > of the modules because I'm primarily doing testing with them by way of > the Debian packaging I'm working on. (Which I'll be able to work on > again after I get done setting back up after my move…) > Could you clarify a little how you did this? You removed the lib/site* folders from the installation package? As long as we don't switch the shebangs to support non-default Perl (/usr/bin/env perl instead of /usr/bin/perl) I think this will cause quite some problems for people who are not using the system-provided Perl? See https://github.com/hollie/misterhouse/pull/249 > >> 'cpanm App::MisterHouse' would be a very nice way to install stable >> MisterHouse versions, isn't it? > > Certainly could be, depending on how it was set up… What exactly do you mean with this? The configuration of the location of the 'data' folders? Kind regards, Lieven. |