Package Details: firefox-kde-opensuse 134.0.2-1

Git Clone URL: https://aur.archlinux.org/firefox-kde-opensuse.git (read-only, click to copy)
Package Base: firefox-kde-opensuse
Description: Standalone web browser from mozilla.org with OpenSUSE patch, integrate better with KDE
Upstream URL: https://github.com/openSUSE/firefox-maintenance
Keywords: browser gecko web
Licenses: GPL, MPL, LGPL
Conflicts: firefox
Provides: firefox
Submitter: csslayer
Maintainer: Thaodan
Last Packager: Thaodan
Votes: 336
Popularity: 0.009062
First Submitted: 2009-12-11 09:10 (UTC)
Last Updated: 2025-02-03 15:56 (UTC)

Required by (180)

Sources (35)

Pinned Comments

Thaodan commented on 2021-04-20 17:40 (UTC) (edited on 2021-04-21 22:45 (UTC) by Thaodan)

If you have issues with this package visit gitlab and read the readme first.

Latest Comments

« First ‹ Previous 1 .. 21 22 23 24 25 26 27 28 29 30 31 .. 140 Next › Last »

simona commented on 2018-01-24 18:41 (UTC) (edited on 2018-01-24 19:13 (UTC) by simona)

==> ERRORE: Makepkg non è riuscito a compilare firefox-kde-opensuse.

==> Riavviare la compilazione di firefox-kde-opensuse [s/N]

==> -------------------------------------------------------

==> cp: impossibile eseguire stat di '/tmp/yaourt-tmp-simona/PKGDEST.KyY /.pkg.': File o directory non esistente

https://pastebin.com/raw/nKW0jpxH

yinflying commented on 2017-12-02 13:59 (UTC)

Good new for me that stays in 56. ff57 is not stable as expected(it will crashed nearly once a day whereas ff56 works stably), ESR version may a good choice, but ff56 may fresher.

YauheniM commented on 2017-11-27 02:04 (UTC) (edited on 2017-11-29 13:23 (UTC) by YauheniM)

Hi, @Thaodan First of all: some old extensions still work in FF57 and even in FF58, if you enable legacy extensions support in the about:config. (but not all and not always correctly) It seems to me that this version should be updated to the 57 because this is the official stable version of the browser which this package should provide, isn't it? So, if some users want to leave the old browser version to save the work of the some add-ons, maybe then: 1. make a separate package for the old version of the browser, because, as it seems to me, it will be more logical than leaving this one, and make another with the new version 2. maybe "old" firefox-kde package should be based on Firefox 52, because 52 is ESR and it has a longer support period than Firefox 56. Best regards, Eugene

renzobenzo commented on 2017-11-27 00:07 (UTC)

I don't understand why this is still v56?

Xavier commented on 2017-11-26 03:29 (UTC)

Hi @Thaodan, I disagree with that policy, the current stable version is the 57, the most add-ons are migrated to webextension, if now some add-ons don't work with v57 they will not soon, and if some users use some no migrated add-ons (I think they are the minority here) if better have other package specific for that like firefox-kde-opensuse-legacy or -v56. If the situation with the old extensions are critical, the arch-devs would not update to v57.

Thaodan commented on 2017-11-25 17:46 (UTC)

Oh sorry I forgot to poste the link to my repo https://gitlab.com/Thaodan/firefox-kde-opensuse/tree/ff57 There you can grab the latest release

snoopy commented on 2017-11-25 17:43 (UTC)

Hi - yeah I had seen that, I think I misunderstood how long that was likely to last. I don't want to speak for anyone else, but personally I can work around broken addons if that's the result of going with 57. I'd be happy to see 56 replaced with 57 now. However, I appreciate your trying to be conservative, not sure how much other folks would be impacted. I'll go back to waiting patiently for the meantime. :-) Thanks!

Thaodan commented on 2017-11-24 22:00 (UTC)

I just put the latest release in a separate branch on gitlab that I already posted a few comments below. I just don't want to break the browser if some user's as most add-ons don't work with this release that change something's where there's no API for. If no one wants this release any more I can overwrite even before add-ons work better. The 57 works and is updated to the latest changes of arch.

snoopy commented on 2017-11-24 20:48 (UTC)

Hi Thaodan. So I'm confused about where we stand based on the comments here. You have everything but aren't sure it's ready yet? This is a fairly anticipated release as I'm sure you've heard. While I appreciate and respect your stewardship of the package - any chance we'll be seeing it soon? Thanks!

« First ‹ Previous 1 .. 21 22 23 24 25 26 27 28 29 30 31 .. 140 Next › Last »