Re: [mh] DateTime::Locale
Paul Onley <[email protected]>
| Newsgroups | gmane.comp.misc.misterhouse.user |
|---|---|
| Message-ID | <[email protected]> |
Thanks Brian, I can understand the original philosophy. For future reference how would one adjust the mh include list to make sure that my modules are used? I guess what I am asking as I'm not that familiar with the guts of mh is where the include list is and can it be easily edited or is it distributed throughout the code? Paul BTW, There is a LOT of mh's core code that I do not use so I would not recommend simply assuming that the shipped Locale.pm doesn't have some modification that some part of mh requires based on my success with replacing it. I may well find I have broken some other part of mh but simply don't use it... YET. On 12/21/20 6:07 PM, Brian M wrote: > Paul, > > There's been much discussion in the past year about the MH philosophy > of including CPAN Perl modules in the distribution. Essentially it > came out of an interest in having MH "just work" out of the box (e.g. > not require a lot of prereqs). This lead to a number of cases where > the core MH worked, but user code used within MH didn't be the user > code was expecting newer versions of modules. > > I undertook a task to move as many of them as I could to a new library > called "fallback", which I placed at the very end of the Perl include > library list so they would only be used as a last resort on systems > that had no newer versions. I moved *lots*, but there were some that > appeared to have been "locally modified" (that is, by some possibly > past MH developer). These were no longer merely predecessors of > current CPAN versions, and I didn't feel I could safely move them > without a lot more study. Given the magnitude of the change I was > making already (and has generally worked quite well for quite a while > now except for a batch of files in bin I forgot to adjust), I decided > not to try to add those into the immediate task. Thus there are a few > really old modules still living in MH's base libraries instead of the > fallback library. I don't have the list of these not-quite-CPAN > modules anymore, but Date::Locale sounds like it fits the bill. If > somebody wants to study it as to compared to the current version and > conclude that the current version is a drop-in replacement for it, I'm > completely fine with moving it to fallback. (Or, someone else can > decide to move them to fallback -- it doesn't have to be just me.) > > In short, MH supplies old versions that haven't been updated in a long > time out of a particular philosophical perspective. Recent work meant > that most of these old versions would be used only as a last resort, > but a few appear to have been modified and those still appear early in > the MH Perl include list. They can be moved to fallback if someone > wants to analyze them and determine that that is a safe thing to do. > > -Brian M > > On 12/21/20 3:00 PM, Paul Onley wrote: >> After downloading the latest Master Branch to try working with the >> Tasmota code I ran into an error trying to start mh. During startup >> mh reports an error that DateTime::Locale 1.06 is required but that >> only 0.34 is available. I had a newer version installed in my perl >> libs but finally found that mh ships with 0.34 in lib/site/DateTime. >> I replaced that Locale.pm with the one in my perl libs and all is >> fine now. Is there a reason that mh ships with the rather old version? >> >> >> >> ________________________________________________________ >> To unsubscribe from this list, go to: >> https://lists.sourceforge.net/lists/listinfo/misterhouse-users >> > > > > ________________________________________________________ > To unsubscribe from this list, go to: > https://lists.sourceforge.net/lists/listinfo/misterhouse-users > ________________________________________________________ To unsubscribe from this list, go to: https://lists.sourceforge.net/lists/listinfo/misterhouse-users