From owner-freebsd-perl@FreeBSD.ORG Sat Sep 25 12:35:02 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 5D0C216A4CE for ; Sat, 25 Sep 2004 12:35:02 +0000 (GMT) Received: from plouf.absolight.net (plouf.absolight.net [212.43.217.12]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1ABE543D41 for ; Sat, 25 Sep 2004 12:35:02 +0000 (GMT) (envelope-from mat@FreeBSD.org) Received: from cc-147.int.t-online.fr (unknown [213.44.125.147]) (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 E29ED4033; Sat, 25 Sep 2004 14:35:00 +0200 (CEST) Date: Sat, 25 Sep 2004 14:34:49 +0200 From: Mathieu Arnold To: Pat Lashley , "Dan Mahoney, System Admin" , users@spamassassin.apache.org, spamassassin-users@incubator.apache.org Message-ID: <2935218715CC0DA42A98E6C2@cc-147.int.t-online.fr> In-Reply-To: References: <20040924043002.Q78840@prime.gushi.org> <2CE7048C26D5B2A38706C484@vanvoght.phoenix.volant.org> <861CEAA9963517079275A510@[192.168.1.5]> X-Mailer: Mulberry/3.1.6 (Win32) MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable 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 12:35:02 -0000 +-le 25/09/2004 02:20 -0700, Pat Lashley =E9crivait : | --On Saturday, September 25, 2004 08:59:03 +0200 Mathieu Arnold | wrote: |=20 |> +-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.) |>=20 |> 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. |=20 | That seems like an awfully short transition period. Why not | a separate 3.0 port for a while; with the old one being deprecated? | Then remove the 2.64 port once the dependant ports have been updated | and in the field long enough for some serious testing? I don't want to have a SA3 port, I'm more in favor of a SA264 port designed for perl 5.005_03 as the databases/p5-DBI-137 port. This is still under discussion. --=20 Mathieu Arnold