From: "Antti Harri" <[EMAIL PROTECTED]>
On Sun, 29 Jan 2006, David Gwynne wrote:
A default configuration is a misconfiguration?
I'd say misconfiguration. Irssi's port in OpenBSD
doesn't create any system wide configuration. And at
least I used that as a base with my updated port.
In /etc/irssi there is only the default theme files
so I'm guessing that such configuration file (with wrong term_charset)
is left-over from previous installations or something similar.
Correct me if I'm wrong..
[EMAIL PROTECTED]:~$ grep term_charset .irssi/config
term_charset = "646";
[EMAIL PROTECTED]:~$ irssi
(process:3027): GLib-CRITICAL **: g_strcasecmp: assertion `s2 != NULL'
failed
[EMAIL PROTECTED]:~$ vim .irssi/config
[EMAIL PROTECTED]:~$ grep term_charset .irssi/config
term_charset = "ISO-8859-1";
[EMAIL PROTECTED]:~$ irssi
[EMAIL PROTECTED]:~$
[EMAIL PROTECTED] loki$ find $HOME/ -name .irssi
[EMAIL PROTECTED] loki$ pkg_info |grep irssi
irssi-0.8.10 modular IRC client with many features (ipv6,socks,proxy)
[EMAIL PROTECTED] loki$ irssi
(process:14716): GLib-CRITICAL **: g_strcasecmp: assertion `s2 != NULL'
failed
[EMAIL PROTECTED] loki$ find $HOME/ -name .irssi
/xhome/loki/.irssi
[EMAIL PROTECTED] loki$
if there is no configuration then irssi creates a default for me. the
default config hits the assertation.
if the problem is that there isn't a valid default config in /etc then
perhaps the port should be set up to provide one on install.
if there is a config file that irssi uses as the template for its config,
then that should be fixed before the pkg is created.
a new install of a package should just work. i don't want to have to tweak
the default config for irssi to work for my users. i just want to go pkg_add
irssi*
it is possible i have an old version of the port. if someone can point me at
the diff that is currently being considered for the ports tree i can try it
out and see if the same thing happens. i may be talking a load of crap if
the newer port is fixed.
dlg
