RE: [misterhouse-users] Debian Package for Misterhouse?

[Bruce W. <br...@mi...>]

> 	I think we could automate something once we get a stable misterhouse
> debian package.  I was thinking we could create packages for each of the
> releases and put them on sourceforge.  However, I think it would
> be great to
> try and get Misterhouse included in the Debian distribution.  This would
> require someone becoming an official debian developer, which is actually
> quite a commitment.  I would be willing to do this if as there is other
> software I help with that I would like included in debian.

This would be cool!  If you are willing, please do give it a try.

> 	Also, because misterhouse is updated so frequently, by the time a
> new debian version was released with misterhouse, it would probably be
> fairly old.  This is something we would probably have to live with.
> Debian's testing process is longer (probably better) than the other
> distributions, which adds to debian's reputation of reliability.
>
> 	As for talking you into "upgrading" to debian,  I was a die hard red
> hat fan until I tried debian.  Debian's packaging system sells itself.  I
> will never go back.  The automatic dependency resolution of apt-get is a
> real time saver.  For those who are hesitant because of debian's
> "difficult"
> installer, I would suggest using Progeny Debian (http://www.progeny.com).
>
> 	Let me know what you think and in the meantime, I will begin work on
> a debian package...

Thanks for the progeny tip.   I'll give it a look.

When you are picking path names for the package, you may want to avoid using
mh.   This might confuse people who are familiar with the 'Mail Handler'
program that is also called mh.  I think newer versions are out with
slightly different names (e.g. xmh).  We debated renaming bin/mh a while
back (e.g. bin/mrh), but at the time the vote was 2 for, 3 against, so I
left it as is.  I figured since we would be keeping all the misterhouse code
in its own directory, it would not matter.

Also, the user-customized .ini file should probably be named misterhouse.ini
(not mh.ini).  Since we point to it with an env var, we can name it whatever
we want.  The default bin/mh.ini should be left as is.

Bruce