From: Michael S. <mi...@st...> - 2013-04-07 13:57:46
|
The last time I looked at this, MH sets up @INC so that the modules in lib/site are not used if similar modules are found in the local system Perl paths. If the Linux distribution includes a module then the one in /lib/site should be benign. From: Vargster [mailto:var...@gm...] Sent: Sunday, April 07, 2013 5:06 AM Cc: The main list for the MisterHouse home automation program Subject: Re: [mh] Distro Question Lee, On Sat, Mar 23, 2013 at 7:32 PM, Vargster <var...@gm...> wrote: > 2) The list of modules used was based on the old install instructions. I'd > guess MH uses it somewhere? My guess is that it's used by a package already needed by MisterHouse (like libberkeleydb-perl) and the correct version would be brought it by that, and therefore having it separately listed is at best misleading. That is true. If you get to the bottom of it, I can change wiki, but can't offer you much help I'm afraid. > 3) No idea, but it seems to work OK on Ubuntu. IIRC, that was in regards to my question about other XS type Perl Modules? I do have the Debian packaging creating a separate 'misterhouse-xs' package; currently it just Recommends the libtext-levenshteinxs-perl package but I also wonder about .what other XS type Perl Modules would be or are useful to MisterHouse. I guess the only way is to remove them and see if MH complains? > Generic instructions are great for people who already understand what's > going on. I was thinking "generic" from the point of view of MisterHouse itself; i.e., what are the modules that MisterHouse depends on, etc; NOT how those modules might be provided for it. Ah, I see what you mean. >.... The original instructions for MH install using CPAN don't work too well under > Ubuntu, that's why the wiki uses the repos, it just works. At least for me, that's the thing: it doesn't just use the repos. I'm still going through them but so far, the majority of the lib/site/* Perl Modules currently in the MisterHouse distribution that I've looked at so far are already packaged for Debian/Ubuntu. Often (as alluded to in another thread) with more recent versions. Yes, this has been mentioned recently in another email. I ran into the same problem a couple years back writing some new code to talk to a solar inverter. It looks like included Perl modules could do with a refresh, or maybe just deleting and using OS supplied modules. Or an install script to download the latest from CPAN? Personally a refresh seems the best ideal as everyone will be running from the same code base? Lee -- Robert J. Clay rj...@gm... |