Date: Tue, 18 Jan 2011 13:13:19 +0100 From: "Julian H. Stacey" <jhs@berklix.com> To: Mark Linimon <linimon@lonesome.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 Message-ID: <201101181214.p0ICDJE4011393@fire.js.berklix.net> In-Reply-To: Your message "Tue, 18 Jan 2011 00:48:50 GMT." <20110118004850.GB17292@lonesome.com>
next in thread | previous in thread | raw e-mail | index | archive | help
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.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?201101181214.p0ICDJE4011393>