From owner-freebsd-ports@FreeBSD.ORG  Tue Jan 18 12:14:13 2011
Return-Path: <owner-freebsd-ports@FreeBSD.ORG>
Delivered-To: ports@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
	by hub.freebsd.org (Postfix) with ESMTP id AF34E106564A;
	Tue, 18 Jan 2011 12:14:13 +0000 (UTC) (envelope-from jhs@berklix.com)
Received: from tower.berklix.org (tower.berklix.org [83.236.223.114])
	by mx1.freebsd.org (Postfix) with ESMTP id 158368FC14;
	Tue, 18 Jan 2011 12:14:12 +0000 (UTC)
Received: from park.js.berklix.net (p5B22EB8A.dip.t-dialin.net [91.34.235.138])
	(authenticated bits=0)
	by tower.berklix.org (8.14.2/8.14.2) with ESMTP id p0ICE10a079247;
	Tue, 18 Jan 2011 12:14:03 GMT (envelope-from jhs@berklix.com)
Received: from fire.js.berklix.net (fire.js.berklix.net [192.168.91.41])
	by park.js.berklix.net (8.13.8/8.13.8) with ESMTP id p0ICDnVY018861;
	Tue, 18 Jan 2011 13:13:51 +0100 (CET) (envelope-from jhs@berklix.com)
Received: from fire.js.berklix.net (localhost [127.0.0.1])
	by fire.js.berklix.net (8.14.3/8.14.3) with ESMTP id p0ICDJE4011393;
	Tue, 18 Jan 2011 13:14:22 +0100 (CET)
	(envelope-from jhs@fire.js.berklix.net)
Message-Id: <201101181214.p0ICDJE4011393@fire.js.berklix.net>
To: Mark Linimon <linimon@lonesome.com>
From: "Julian H. Stacey" <jhs@berklix.com>
Organization: http://www.berklix.com BSD Unix Linux Consultancy, Munich Germany
User-agent: EXMH on FreeBSD http://www.berklix.com/free/
X-URL: http://www.berklix.com
In-reply-to: Your message "Tue, 18 Jan 2011 00:48:50 GMT."
	<20110118004850.GB17292@lonesome.com> 
Date: Tue, 18 Jan 2011 13:13:19 +0100
Sender: jhs@berklix.com
Cc: ports@freebsd.org, rene@freebsd.org, Chad Perrin <perrin@apotheon.com>,
	"Gary Jennejohn \(Home\)" <gljennjohn@googlemail.com>
Subject: Re: www/chromium MAINTAINER,
	was Re: chromium producing constant hdd access 
X-BeenThere: freebsd-ports@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Porting software to FreeBSD <freebsd-ports.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-ports>,
	<mailto:freebsd-ports-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-ports>
List-Post: <mailto:freebsd-ports@freebsd.org>
List-Help: <mailto:freebsd-ports-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-ports>,
	<mailto:freebsd-ports-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Tue, 18 Jan 2011 12:14:13 -0000

Hi,
Reference:
> From:		Mark Linimon <linimon@lonesome.com> 
> Date:		Tue, 18 Jan 2011 00:48:50 +0000 
> Message-id:	<20110118004850.GB17292@lonesome.com> 

Mark Linimon wrote:
> On Mon, Jan 17, 2011 at 08:12:40PM +0100, Julian H. Stacey wrote:
> > rene@ has ignored request to roll back.  If rene@ resigns,
> > MAINTAINER would revert to ports@freebsd.org so others could fix
> > FreeBSD's current ports/www/chromium
> 
> Because of the legal questions surrounding chromium,

I know nothing of that. Just that a month ago it compiled, now it won't.

> portmgr will ensure
> that it does not revert to ports@ :-)
> mcl

So how about:
	Revert to something that will compile, with no MAINTAINER.
	Or delete port ?
		A port that 
			- wont build, 
			- the maintainer won't fix, 
			- has security issues, 
			- is legaly problematic
			- ports@ is scared of inheriting
			- that we can't fix by adding a _DEPENDS etc
		seems a waste of time & name space,

Cheers,
Julian
-- 
Julian Stacey, BSD Unix Linux C Sys Eng Consultants Munich http://berklix.com
	Mail plain text;  Not quoted-printable, or HTML or base 64.
	Avoid top posting, it cripples itemised cumulative responses.