Date: Fri, 17 Apr 2015 13:43:17 -0400 From: Timothy Vaccarelli <tmvfroid@gmail.com> To: chromium@freebsd.org Subject: Re: Chromium 41.0.2272.118 Update Message-ID: <CANFjoWhOKedK547pgZPMviCafMZE_xEiq2wv52cHc3BjFD69Kw@mail.gmail.com> In-Reply-To: <CANFjoWj=AXBCEQ7LAqnXqkNFQpZ%2BMSZDpzEpOo-XatYWSJYLTA@mail.gmail.com> References: <CANFjoWj=AXBCEQ7LAqnXqkNFQpZ%2BMSZDpzEpOo-XatYWSJYLTA@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Just as a follow-up, the issue I mentioned earlier regarding the icudtl.dat file has been fixed. The only two things I can think of that haven't been tested are how this port builds on a 32 bit system, and whether or not the extra-patch-gcc file will work as it is since I do not use gcc and haven't tested that particular patch. On Thu, Apr 16, 2015 at 9:57 AM, Timothy Vaccarelli <tmvfroid@gmail.com> wrote: > Hello, > Recently I tried installing chromium from FreeBSD's port system, to find > out that the version included there was marked as vulnerable. > In order to get around this, I took the patch files for chromium and over > the last couple of days updated them to work for version 41.0.2272.118 > > I would appreciate it if you could use my patches to update chromium on > the ports tree. There is only one issue that I noticed with the update -- > for some reason chromium won't launch without the file icudtl.dat which I > had to manually copy over to work. Other than that everything seems fine > with the port. > > You can find my work at https://github.com/LeFroid/chromium > > All the best >
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CANFjoWhOKedK547pgZPMviCafMZE_xEiq2wv52cHc3BjFD69Kw>