Skip site navigation (1)Skip section navigation (2)
Date:      Tue, 18 Jan 2011 15:24:48 +0100
From:      =?ISO-8859-1?Q?Ren=E9_Ladan?= <rene@freebsd.org>
To:        "Julian H. Stacey" <jhs@berklix.com>
Cc:        ports@freebsd.org, Mark Linimon <linimon@lonesome.com>, 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:  <AANLkTin6nrQ8TzE9XU=mqL6YtT849K0dnRqLSsd0RM%2BT@mail.gmail.com>
In-Reply-To: <201101181214.p0ICDJE4011393@fire.js.berklix.net>
References:  <20110118004850.GB17292@lonesome.com> <201101181214.p0ICDJE4011393@fire.js.berklix.net>

next in thread | previous in thread | raw e-mail | index | archive | help
2011/1/18 Julian H. Stacey <jhs@berklix.com>:
> Hi,
> Reference:
>> From: =A0 =A0 =A0 =A0 Mark Linimon <linimon@lonesome.com>
>> Date: =A0 =A0 =A0 =A0 Tue, 18 Jan 2011 00:48:50 +0000
>> Message-id: =A0 <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. =A0If 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:
> =A0 =A0 =A0 =A0Revert to something that will compile, with no MAINTAINER.
> =A0 =A0 =A0 =A0Or delete port ?
> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0A port that
> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0- wont build,
FORBIDDEN is there for a reason [*]
> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0- the maintainer won't fix=
,
makes no sense, versions before 8 are unsupported upstream,
> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0- has security issues,
not my fault ...
> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0- is legaly problematic
there are proper methods to handle this, the issue is mostly upstream,
> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0- ports@ is scared of inhe=
riting
ports@ is an indication that the port is unmaintained, except for a few
well-known exceptions (misc/compat??)
> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0- that we can't fix by add=
ing a _DEPENDS etc
makes no sense, see above

[*] maybe all currently vulnerable ports should be marked FORBIDDEN, and ye=
s,
this includes a dependency for linux-flash-plugin

Regards,
Rene



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?AANLkTin6nrQ8TzE9XU=mqL6YtT849K0dnRqLSsd0RM%2BT>