![]() ![]() Now, the announcement does not mention the availability of an update, Waterfox Classic's previous update was released on October 13th. Hopefully we will see other contributors chipping in to the project to ease the burden. Kontos has done a commendable job in maintaining Waterfox for over 10 years, and it can't be easy to work on two projects at the same time. That is not a very reassuring message, although it is quite understandable and the transparency is appreciated. Waterfox Classic will warn the user that the browser could be vulnerable to multiple security issues, and it is up to the user to decide whether to proceed to user it or not. These changes are expected to go live this week. ![]() The announcement also says that Waterfox Classic will have its own page on the official site, this is something which has bothered some users, as the lone mention of it, has been the link to the releases page, from which you can download the browser. A list of unpatched security issues will be made available on the browser's website. The developer says that Waterfox Classic's future will rely on contributions, by which he probably means what he previously mentioned, about porting security fixes from Firefox ESR. And since it is no longer tied with G4, issues won't be closed because of complications/incompatibilities with the modern version. Now that Waterfox Classic has its own Github repository, users will be able to track and report issues related specifically to it. But more importantly, this will improve the development process of the browser, because previously, issues related to both versions were tackled together. Firstly, users who relied on it will get new versions. This is a welcome move for multiple reasons. The developer cites that it has been difficult to keep the browser up to date with the main project, which is why the two variants have been diverged. Kontos has confirmed that Waterfox Classic will continue to be supported, but it will exist as a separate open-source project from Waterfox G4. Waterfox Classic development will continue No wonder users started worrying, but if you were among them, you can rest assured that it is still being worked on. He had mentioned that its future depended on the ease of porting security fixes from Firefox ESR. There were no instruction sets explicitly for Kubuntu.Alex Kontos, the developer of the popular Firefox fork, had previously hinted that the Waterfox Classic version was not a priority. I am assuming that even though the distros mentioned in the steps were xUbuntu they applied to Kubuntu also. no broken installations at the command line). Status:Error: Cannot satisfy dependenciesĪll the steps completed as expected (i.e. Running waterfox-g4-kde_0.5.1-0+57.1_b from QApt Package Installer I receive a message: I grabbed the package for Packages for xUbuntu 18.04 and installed waterfox-g4-kde_0.5.1-0+57.1_b Moving back to the README, I chose Click to see instructions for waterfox-g4-kde, clicked the Ubuntu logo and chose Add repository and install manually following the steps under "For xUbuntu 18.04 run the following" I grabbed the package for Packages for xUbuntu 18.04 and installed waterfox-classic-kde_2021.11-0+79.1_b I followed the link Click to see instructions for waterfox-classic-kde, clicked the Ubuntu logo and chose Add repository and install manually, following the steps under "For xUbuntu 18.04 run the following" ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |