Chromium (slarm64 , aarch64)
|
|
|
|
|
Thanks I'll keep that in mind . My kit hasn't arrived yet
|
|
Is this chromium, or chromium-ungoogled?
|
Quote:
the ungoogled patch package will be called ungoogled-chromium |
Thanks. I'll wait.
|
|
Quote:
Quote:
|
|
:thumbsup:
Thanks, sndwvs. |
All your extra packages seem to be built on Current. That's not good for a guy like me who tried to stay on 15.0, because this sort of thing happens:
Code:
dec@SparrowFart:~/Downloads$ ldd /usr/lib64/chromium/chromium |grep found If you're not doing packages for 15.0, I'd probably be better updating to Current fairly often, wouldn't I? I have a stable release, but no extra packages. |
Quote:
|
Hmmph! Right. Duly noted.
I'll leave it until the 6.2.x kernels come along with their enhanced graphics. Please wait for at least 6.2.0.1 because those sort of things always seem to give out their bugs once the masses get their hands on them. I'll evidently have to start keeping an eye on the ChangeLog too, as packages are dropped and new ones stuck in. Alien Bob had me kind of spoiled because his x86_64 repo has 15.0 & current. EDIT: [Looking at ChangeLog] All I need is a smart line with sed to delete every entry in the ChangeLog with "Upgraded" or "Rebuilt" in them, and I'm left with the ones you added or dropped. Alternatively I could just grep for 'Added' or 'Dropped' which is probably lazier. |
On Chromium-107.<whatever>:
It's on Alien Bob's blog (or blurb) that chromium-107 was a quick fix to patch something being used in the wild. But in closing one door, it opened another. I'm posting this from x86_64 on Ungoogled-Chromium-108.0.5359.94, which patches the new fault introduced on 107.<whatever>. It might be good to get that one instead. |
|
|
|
What glibc is that compiled against? I'm on 2.33 here. I just dread all the work changing things over and my neat little shortcuts that I had worked out to update.
|
Quote:
|
Quote:
|
|
irradium chromium#124.0.6367.118-1.pkg.tar.gz
|
All times are GMT -5. The time now is 04:23 PM. |