On Friday 09 May 2014, Wolfgang Rosenauer wrote:
Am 09.05.2014 15:59, schrieb Ruediger Meier:
On Friday 09 May 2014, Wolfgang Rosenauer wrote:
Am 09.05.2014 15:06, schrieb Ruediger Meier:
has anybody already tried to build firefox and firefox-esr packages so that they are installable in parallel?
I haven't really tried but it shouldn't be that hard for the basic stuff.
If you would try I'd be glad to test it for openSUSE 13.1.
I'd really like to have ESR available officially in openSUSE, see https://bugzilla.novell.com/show_bug.cgi?id=790664
Not me to decide but packages are available and easily included for Factory if that's the decision.
Maybe just try to submit request ESR against Factory? The question is whether you would like to maintain another package during openSUSE release life time.
No, I don't from my side. But I maintain it currently anyway with the difference that nobody forces me. So again if there is really a demand for it I might consider it but so far I'm not sure if there is.
It would be even more nice if both version could be installed in parallel to let the user decide which one to use.
Not sure about this one. Following your argument from bugzilla you don't want rapid changes. Then just decide which one to use but don't ask me to provide the same package multiple times just for name and installation location changes.
In doubt I (as the admin) would decide to install ESR but I have both conservative users and others who want to have new features. For example many of my users have locally installed browers because I don't provide them what they want. That's bad because they certainly don't update regulary for securety updates.
Also would be nice to be able to test broken websites with alternative versions quickly. This may be even more important for web developers who want to test their own sites at least with all officially living browser (and ESR is a very important one).
But in case that enough people support and request this I could be convinced still.
Another option whithout more maintenance work would be to use _only_ ESR in Factory. For example we could still update to version 30 and then to the next ESR (31). This would be IMO already much better than having only the latest.
Not sure if that is the case. Then I hear already people jumping to Chromium because Firefox "is too old on openSUSE".
I've wasted hours today because of update 29 and I know that I'll have to do it again next month. That's IMO not a good default and even more bad that we don't provide an official alternative. But maybe this is all debatable. Let's do a first step (before discussing whether only ESR or latest or both should be supported and what should be the default) Could I just submit request mozilla/firefox24esr against openSUSE:Factory/MozillaFirefoxESR or should we go through mozilla:Factory project? Would the renamed package build in Factory without problems? What would be a good name? 1. MozillaFirefoxESR 2. MozillaFirefox-ESR 3. MozillaFirefox-esr I prefer first one.
Again, I'm providing both anyway in the buildservice and I can only work with the data I have and the number of complaints (the ones I see) are very low about the rapid updates of Firefox.
Don't forget all the Evergreen users. They don't complain because they _have_ already esr. I started complaining just now because I've switched the first machine to 13.1 last month. cu, Rudi -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org