From owner-freebsd-perl@FreeBSD.ORG Sat Sep 25 06:59:07 2004 Return-Path: Delivered-To: freebsd-perl@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id A2FC816A4CE for ; Sat, 25 Sep 2004 06:59:07 +0000 (GMT) Received: from plouf.absolight.net (plouf.absolight.net [212.43.217.12]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6907343D1D for ; Sat, 25 Sep 2004 06:59:07 +0000 (GMT) (envelope-from mat@mat.cc) Received: from pouet.in.mat.cc (pouet.in.mat.cc [193.30.224.122]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by plouf.absolight.net (Postfix) with ESMTP id B596B4005; Sat, 25 Sep 2004 08:59:05 +0200 (CEST) Date: Sat, 25 Sep 2004 08:59:03 +0200 From: Mathieu Arnold To: Pat Lashley , "Dan Mahoney, System Admin" , users@spamassassin.apache.org Message-ID: <861CEAA9963517079275A510@[192.168.1.5]> In-Reply-To: <2CE7048C26D5B2A38706C484@vanvoght.phoenix.volant.org> References: <20040924043002.Q78840@prime.gushi.org> <2CE7048C26D5B2A38706C484@vanvoght.phoenix.volant.org> X-Mailer: Mulberry/3.1.6 (Win32) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Content-Disposition: inline cc: perl@freebsd.org Subject: Re: FreeBSD port of SpamAssassin 3.0.0 (continued) X-BeenThere: freebsd-perl@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: maintainer of a number of perl-related ports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 25 Sep 2004 06:59:07 -0000 +-Le 24/09/2004 18:20 -0700, Pat Lashley a dit : | SA 3.0 should probably be a separate port rather than an update | to the existing SA port; due to the lack of backwards compatability | in the API. For example, it would break the Exim port which by | default includes the ExiScan patches. (The Exim port would still | build; but the SpamAssassin support would fail at run time.) I don't think we will keep the old spamassassin. The 2.64 version will be the only one working with 5.005_03, but well... It's not possible to have SA3 work with 5.005_03 (believe me, I tried). So, a few days before committing the SA3 update, I'll send a mail with the patch I plan to commit to maintainers of ports depending on SA264 for them to update/patch/whatever. -- Mathieu Arnold