![]() (After all, this is the main Slackware advantage as I see it – one can support themselves in the sense of backporting needed fixes, and even complex tasks like building a browser, notwithstanding how cumbersome it can be to prepare, are a viable option for those, who have good reasons why not to rely on the builds done by someone else…).ītw, could you elaborate a bit about the burden the 14.2 (32bit) builds of these newest chromium releases pose? Should one expect to create handmade fixes for failing builds like every second canary release or something like that? I have prepared patches for/built the Seamonkey myself in the past, will build Chromium myself too. So I guess it would be good if you’d leave the 14.2 slackbuild sources (if not the builds) of your last 14.2 chromium builds up for download even after 2nd February, so that people who are able to build the package themselves, can continue to do so (a.k.a. ![]() It will eventually happen, but certainly not on Feb 2nd. I’m interrested in those, too.ītw, I’m not going to upgrade to 15.0 anytime soon for a plethora of reasons (time constraints and workload – need to avoid splitting my task for maintaining different sets of production system versions – the number of those I maintain is a 2digit number – and a huge amount of changes I’d need to research first in order to reach the same working environment I depend on, on my desktop, etc.). He is probably asking about availability of your slackbuild sources for 14.2, not for the resulting builds. If you did upgrade yet but still want to use my Chromium browser packages, you still have two months’ time to prepare and execute that upgrade.Ĭhromium packages for Slackware 15.0 and -current will of course keep coming. On that day, Slackware 15.0 is one year old and I expect that everybody who uses a graphical desktop on Slackware, will have upgraded from Slackware 14.2 to 15.0 during that year. I will stop releasing Chromium packages for Slackware 14.2 after February 2nd, 2023. Target OS releases are Slackware 14.2 and higher (32bit and 64bit). I grabbed the new source tarballs and built 1.94 in the course of the weekend.Īnd I have now uploaded new packages both for chromium and chromium-ungoogled. Luckily someone alerted me to the security fix in the comments section of my previous post. ![]() The intermediate release took me by surprise. On friday, I had finally built and uploaded Slackware packages for this, when they released a quick fix to plug an already actively exploited hole (CVE-2022-4262).
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |