www/chromium MAINTAINER, was Re: chromium producing constant hdd access

[Julian H. Stacey]

Hi ports at freebsd.org &
cc GaryJ & rene@
bcc: freebsd-questions at freebsd.org

The hdd access thread could continue on questions@ so I left that BCC'd
but issue of MAINTAINER of www/chromium best on ports@ list.

Reference:
> From:		Chad Perrin <perrin at apotheon.com> 
> 
> On Sun, Jan 16, 2011 at 11:51:43AM +0000, Alexander Best wrote:
> > hi there,
> >=20
> > i noticed chromium is producing a lot of hdd activity. i think it writes =
> every
> > 1kb of new data directly to disk or so. is there a way to increase chromi=
> ums
> > download buffer somehow. firefox or opera seem to have a much larger down=
> load
> > buffer and write bigger chunks to disk. thus they produce a lot less hdd =
> writes
> > per second.
> >=20
> > has anybody experienced the same behavior?
> 
> I haven't used the Chromium browser in months, since a bunch of
> vulnerabilities arose and the port maintainer's business model evidently
> makes it impossible for him to update the port to fix vulnerabilities
> that are less than a year old.

ports/www/chromium "MAINTAINER" rene@ (cc'd) leaves it broken (see
mail below), it still won't even compile (I just checked again a
week later).  A CVS roll back would at least get it compiling again,
rene@ has ignored request to roll back.  If rene@ resigns,
MAINTAINER would revert to ports at freebsd.org so others could fix
FreeBSD's current ports/www/chromium

--------
] To: =?ISO-8859-1?Q?Ren=E9_Ladan?= <rene at freebsd.org>
] cc: "Gary Jennejohn (Home)" <gljennjohn at googlemail.com>
] Subject: Re: /pri/FreeBSD/branches/amd64/-current/ports/www/chromium 
] From: "Julian H. Stacey" <jhs at berklix.com>
] cc: "Julian H. Stacey" <jhs at berklix.com>
] Date: Mon, 10 Jan 2011 18:51:26 +0100
] Sender: jhs at berklix.com
] 
] Hi,
] Reference:
] > From:		=?ISO-8859-1?Q?Ren=E9_Ladan?= <rene at freebsd.org> 
] > Date:		Mon, 10 Jan 2011 18:06:37 +0100 
] > Message-id:	<AANLkTimgs7dVK=6-nmgfNVN18w3wMARdE_VWBKnLp_5S at mail.gmail.com> 
] 
] =?ISO-8859-1?Q?Ren=E9_Ladan?= wrote:
] > 2011/1/10 Julian H. Stacey <jhs at berklix.com>:
] > > Hi Rene cc Gary,
] > >
] > > =?ISO-8859-1?Q?Ren=E9_Ladan?= wrote:
] > >> 2011/1/10 Julian H. Stacey <jhs at berklix.com>:
] > >> > Hi rene at FreeBSD.org
] > >> > cc Gary J
] > >> >
] > >> > FYI as maintainer of chromium
] > >> >
] > >> > cd /pri/FreeBSD/branches/amd64/-current/ports/www/chromium
] > >> > setenv PORTSDIR /pri/FreeBSD/branches/amd64/-current/ports
] > >> > uname -a
] > >> > FreeBSD fire.js.berklix.net 8.0-RELEASE FreeBSD 8.0-RELEASE #0: Mon Jul 12 00:59:43 CEST 2010     jhs at fire.js.berklix.net:/usr1/src/sys/amd64/compile/FIRE64.small  amd64
] > >> > make
] > >> >        ===>  chromium-6.0.472.63 cannot install: Unknown component dconf.
] > >> >
] > >> > I have built chromium before on this box,
] > >> >        "About" key reports: 6.0.472.63(0)
] > >> >        /var/db/pkg/chromium-6.0.472.63
] > >> >
] > >> > It won't rebuild now though,
] > >> > ( I was trying to rebuild to make package for a friend cc'd Gary
] > >> >  who runs current, chrome doesnt build for him too apparently )
] > >> >
] > >> Currently the version of Chromium in the Ports Collection is marked as
] > >> FORBIDDEN because of security problems, and the source distribution
] > >> tarball is unavailable.
] > >>
] > >> There should be a new version (9.0) available
] > >> soonish though.
] > >>
] > >> Rene
] > >
] > > If chromium generic team fix security issues,
] 
] You lost text from my reply, here it is again:
] 
] ] ] If chromium generic team fix security issues, but still use
] ] ] dconf, that may still leave you needing to fix the FreeBSD Makefile
] ] ] to fix the dconf build dependency failure ?  I have source here if
] ] ] you want it, so you can fix that in parallel to save waiting.
] ] ] 
] ] ] 	95188168 Nov 12 11:29 chromium-courgette-redacted-6.0.472.63.tar.xz
] ] ] 	MD5 (chromium-courgette-redacted-6.0.472.63.tar.xz) = adb9186424fa1800eef49cd14329821e
] ] ] 
] ] ] My binaries were localy built here by me using current Makefile, so I presume
] ] ] someone broke current Makefile after that, possibly before it was
] ] ] marked forbidden (which I hashed out) ?  Unless its eg my local
] ] ] env/ libs or something broke since I built it.
] ] ] 
] ] ] Dates of my builds:
] ] ] 
] ] ] -r-xr-xr-x  1 root  wheel  63947372 Nov 24 09:43 /usr/local/share/chromium/chrome*
] ] ] amd64
] ] ] 
] ] ] -r-xr-xr-x  1 root  wheel  56994655 Nov 25 00:57 /usr/local/share/chromium/chrome*
] ] ] i686
] 
] 
] > They  only fix them for the current stable/beta/dev (8/9/10)
] > versions of Chromium. The old maintainer ported obsolete versions
] 
] Which built & runs.
] 
] > of Chromium unless you paid for them.
] 
] I paid nothing, it built & runs.
] 
] > Currently there is no free version of Chromium on FreeBSD.
] 
] Who broke ports/www/chromium build some time after 25 Nov 2010 ?
] As Maintainer, please back out CVS commits till it builds again,
] (leave it marked as FORBIDDEN= if you choose), 
] only recommit changes when you have sources that build.
-------------------

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.