Re: chrome package question

From: Pete Wright <pete_at_nomadlogic.org>
Date: Tue, 03 Jan 2023 00:41:52 UTC

On 1/2/23 14:48, Doug Denault wrote:
> On Mon, 2 Jan 2023, Steve O'Hara-Smith wrote:
>
>> On Mon, 2 Jan 2023 21:37:06 +0000 (UTC)
>> doug <doug@safeport.com> wrote:
>>
>>> I am using 12.3-RELEASE FreeBSD 12.3-RELEASE r371126. This is 
>>> running on
>>> my iMac and that was the USB image I had handy. I will upgrate to 12.4
>>> eventually. Still ....
>>
>>     Yep I'm seeing the same from a 12.3 box, looks like the package
>> isn't there for 12.3 - odd it's not EOL yet (quite).
>
> Thanks Steve. Not going to be fixed and I need to get to 12.4 anyway. 
> Always nice to know it ain't just me.   :)
>
I've found that periodically Chromium will run into build issues in 
freebsd making packages unvailable.  there are two ways i've worked 
around this:

1. locking the chromium package to ensure it never gets accidentally 
uninstalled, then making sure a pkg is avail in the repos before upgrading

2. run linux-chrome.  i've found this to be really stable on my end and 
is my preferred setup for times firefox won't cut it
     - https://github.com/mrclksr/linux-browser-installer

the linux-chrome route has the added benefit of supporting widevine, 
thus allowing you to use netflix, spotify etc on freebsd.  for me it's 
worth the slight hassle of running things via an ubuntu jail.

-pete

-- 
Pete Wright
pete@nomadlogic.org
@nomadlogicLA