From owner-freebsd-ports@FreeBSD.ORG Sat Feb 19 10:53:13 2005 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1E23A16A4CE for ; Sat, 19 Feb 2005 10:53:13 +0000 (GMT) Received: from bloodwood.hunterlink.net.au (smtp-local.hunterlink.net.au [203.12.144.17]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5B3CE43D31 for ; Sat, 19 Feb 2005 10:53:11 +0000 (GMT) (envelope-from boris@brooknet.com.au) Received: from ppp2782.dyn.pacific.net.au (ppp2782.dyn.pacific.net.au [61.8.39.130])j1JAr7nw006000 for ; Sat, 19 Feb 2005 21:53:08 +1100 From: Sam Lawrance To: ports@freebsd.org Content-Type: text/plain Date: Sat, 19 Feb 2005 21:54:14 +1100 Message-Id: <1108810454.670.35.camel@dirk.no.domain> Mime-Version: 1.0 X-Mailer: Evolution 2.0.1FreeBSD GNOME Team Port Content-Transfer-Encoding: 7bit Subject: Update or remove X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 19 Feb 2005 10:53:13 -0000 These ports have fixable fetch problems. I'd like suggestions on what to do with them. I'm thinking remove them for the reasons below, but maybe that's a bad idea somehow: gmime-1.0.7_1 /usr/ports/mail/gmime Library (written in C) for parsing and creating messages using MIME Could update to 1.0.8, but nothing in the tree uses it. gmime-2 seems to be the active choice. libspf-0.25.b /usr/ports/mail/libspf Sender Policy Framework (SPF) library and client Could update to libspf-1.0.0rc6, but again nothing uses it. libspf2 looks to be a more popular choice.