From owner-freebsd-gnome@FreeBSD.ORG  Mon Mar  5 21:24:48 2007
Return-Path: <owner-freebsd-gnome@FreeBSD.ORG>
X-Original-To: gnome@freebsd.org
Delivered-To: freebsd-gnome@FreeBSD.ORG
Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52])
	by hub.freebsd.org (Postfix) with ESMTP id AF23716A403
	for <gnome@freebsd.org>; Mon,  5 Mar 2007 21:24:48 +0000 (UTC)
	(envelope-from gpalmer@freebsd.org)
Received: from noop.in-addr.com (noop.in-addr.com [208.58.23.51])
	by mx1.freebsd.org (Postfix) with ESMTP id 88A5613C4C2
	for <gnome@freebsd.org>; Mon,  5 Mar 2007 21:24:48 +0000 (UTC)
	(envelope-from gpalmer@freebsd.org)
Received: from gjp by noop.in-addr.com with local (Exim 4.54 (FreeBSD))
	id 1HOKUB-000C22-QI
	for gnome@freebsd.org; Mon, 05 Mar 2007 16:12:47 -0500
Date: Mon, 5 Mar 2007 16:12:47 -0500
From: Gary Palmer <gpalmer@freebsd.org>
To: gnome@freebsd.org
Message-ID: <20070305211247.GA32936@in-addr.com>
Mail-Followup-To: gnome@freebsd.org
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Cc: 
Subject: [www/seamonkey] Not possible to disable chatzilla
X-BeenThere: freebsd-gnome@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: GNOME for FreeBSD -- porting and maintaining
	<freebsd-gnome.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-gnome>,
	<mailto:freebsd-gnome-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-gnome>
List-Post: <mailto:freebsd-gnome@freebsd.org>
List-Help: <mailto:freebsd-gnome-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-gnome>,
	<mailto:freebsd-gnome-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Mon, 05 Mar 2007 21:24:48 -0000

Hi,

My port config for www/seamonkey does not have the checkbox next to the
"Enable the Chatzilla IRC module" option set, and yet if I build seamonkey
chatzilla is included.  I believe this is due to chatzilla being moved to
being a "default" extension in recent versions of SeaMonkey.

Could the port be updated to handle the new state of affairs please?

Thanks,

Gary