From owner-freebsd-ports Tue Jan 22 9:33:18 2002 Delivered-To: freebsd-ports@freebsd.org Received: from mail.tgd.net (pop3-ssl.tgd.net [209.81.25.10]) by hub.freebsd.org (Postfix) with ESMTP id 4179A37B47F for ; Tue, 22 Jan 2002 09:33:07 -0800 (PST) Received: by mail.tgd.net (Postfix, from userid 1001) id E55E720F07; Tue, 22 Jan 2002 09:33:06 -0800 (PST) Date: Tue, 22 Jan 2002 09:33:06 -0800 From: Sean Chittenden To: freebsd-ports@freebsd.org Subject: Re: ports/34156: Upgrade jabber Message-ID: <20020122093306.D928@ninja1.internal> References: <200201221639.g0MGdkK32845@freefall.freebsd.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5.1i In-Reply-To: <200201221639.g0MGdkK32845@freefall.freebsd.org>; from "sf@FreeBSD.org" on Tue, Jan 22, 2002 at = 08:39:46AM X-PGP-Key: 0x1EDDFAAD X-PGP-Fingerprint: C665 A17F 9A56 286C 5CFB 1DEA 9F4F 5CEF 1EDD FAAD X-Web-Homepage: http://sean.chittenden.org/ Sender: owner-freebsd-ports@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org 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