From owner-cvs-ports@FreeBSD.ORG Mon Mar 29 08:33:11 2004 Return-Path: Delivered-To: cvs-ports@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 09A1816A4CE; Mon, 29 Mar 2004 08:33:11 -0800 (PST) Received: from gw.celabo.org (gw.celabo.org [208.42.49.153]) by mx1.FreeBSD.org (Postfix) with ESMTP id B463943D39; Mon, 29 Mar 2004 08:33:10 -0800 (PST) (envelope-from nectar@celabo.org) Received: from madman.celabo.org (madman.celabo.org [10.0.1.111]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "madman.celabo.org", Issuer "celabo.org CA" (not verified)) by gw.celabo.org (Postfix) with ESMTP id 55ACE54883; Mon, 29 Mar 2004 10:33:10 -0600 (CST) Received: by madman.celabo.org (Postfix, from userid 1001) id E10DB6D455; Mon, 29 Mar 2004 10:33:09 -0600 (CST) Date: Mon, 29 Mar 2004 10:33:09 -0600 From: "Jacques A. Vidrine" To: Oliver Eikemeier Message-ID: <20040329163309.GA81526@madman.celabo.org> Mail-Followup-To: "Jacques A. Vidrine" , Oliver Eikemeier , ports-committers@FreeBSD.org, cvs-ports@FreeBSD.org, cvs-all@FreeBSD.org References: <200403282344.i2SNi6Hq047722@repoman.freebsd.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200403282344.i2SNi6Hq047722@repoman.freebsd.org> X-Url: http://www.celabo.org/ User-Agent: Mutt/1.5.6i cc: cvs-ports@FreeBSD.org cc: cvs-all@FreeBSD.org cc: ports-committers@FreeBSD.org Subject: Re: cvs commit: ports/multimedia/xine Makefile X-BeenThere: cvs-ports@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: CVS commit messages for the ports tree List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 29 Mar 2004 16:33:11 -0000 On Sun, Mar 28, 2004 at 03:44:06PM -0800, Oliver Eikemeier wrote: > eik 2004/03/28 15:44:06 PST > > FreeBSD ports repository > > Modified files: > multimedia/xine Makefile > Log: > Mark forbidden due to an entry in the VuXML database. Don't > forget to add the version which fixes the issues there. FWIW: I didn't mark this port FORBIDDEN when I added the issue to the database because some issues are not very severe. For example, this issue has practically no impact on single user systems, and quite possibly no impact on any FreeBSD user anywhere. Marking the port FORBIDDEN in this case seems extreme. I'd prefer to reserve FORBIDDEN for those cases where the ports present some danger. Those who want a more strict policy can use portaudit or similar, right? > http://people.freebsd.org/~eik/portaudit/fde53204-7ea6-11d8-9645-0020ed76ef5a.html By the way, I'd appreciate it if you'd point to the VuXML site instead (the URLs are `permanent'). http://vuxml.freebsd.org/ http://vuxml.freebsd.org/fde53204-7ea6-11d8-9645-0020ed76ef5a.html Cheers, -- Jacques Vidrine / nectar@celabo.org / jvidrine@verio.net / nectar@freebsd.org