Date: Tue, 22 Jan 2002 09:33:06 -0800 From: Sean Chittenden <sean@chittenden.org> To: freebsd-ports@freebsd.org Subject: Re: ports/34156: Upgrade jabber Message-ID: <20020122093306.D928@ninja1.internal> In-Reply-To: <200201221639.g0MGdkK32845@freefall.freebsd.org>; from "sf@FreeBSD.org" on Tue, Jan 22, 2002 at = 08:39:46AM References: <200201221639.g0MGdkK32845@freefall.freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
For those that use Jabber, I've got a quick question in terms of
preferences. Jabber has 5-6 transports that are included in it by
default right now. Right now you have no choice but to load all of
the transports and adding new transports is a PITA (group transport is
horked right now: needs automake14, but the rest of the port doesn't,
same with the updated version of yahoo transport). I'd like to do one
of two things and want to solicit opinions:
1) Use dialog to create a multi-select prompt to let the user decide
what transports and options they want (ex: ssl, yahoo, group, jud,
etc) and then compile jabber accordingly
2) Most of the jabber transports are so's and can be broken into their
own respective transports (ex: jabber-yahoo-transport, jabber-jud,
jabber-aim-transport). The only catch with this is that some of
the transports require a few headers from jabber that aren't
installed.
I'm personally a fan of option #2, providing a knob called WITHOUT_SSL
for the SSL example in #1, and still breaking the transports out into
their own ports. Thoughts from someone who uses jabber? There are
currently many transports available (~25), and even alternate
transports (ex: ICQ). I'd like to get that decision making out of
the maintainer's hands and into the users control. Thoughts? -sc
http://www.jabber.org/?oid=72
--
Sean Chittenden
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-ports" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20020122093306.D928>