On 18 Oct 2017 13:21, "James Hogarth" <james.hogarth@xxxxxxxxx> wrote:
On 17 Oct 2017 17:40, "Gerald B. Cox" <gbcox@xxxxxx> wrote:On Tue, Oct 17, 2017 at 1:33 AM, James Hogarth <james.hogarth@xxxxxxxxx> wrote:And even if we hypothetically forked Firefox (as that is what it would be) to add legacy extension capability back it would mark a significant divergence with upstream and I'm not sure if addons.mozilla.org could even be used then anyway as it'd detect FF57 and state that older extensions are not supported. That doesn't even go into the legal situation as to whether we could even call it Firefox with such divergence (remember Iceweasel?) ... there's a reason there's a whitelist on the Firefox packages for build permissions after all.And how long would you want FF packagers to maintain such a patchset for? Even the next ESR will drop legacy extensions.Yup! It's a non-starter. Mozilla knows exactly what they are doing - and have made their decision.To keep interested parties here in the loop...The COPR is operational and a draft for review has been entered into the magazine with details for this preview on the magazine mailing list.I'll keep the COPR updated as best I can with any changes to the the Fedora 27 package... may lag by a day or so but I'll do my best ;)Note that although there are F25 builds in the COPR there will be no Firefox 57 builds going into the official F25 repos so that one really is no support and just there to ease testing.I'll keep the COPR running and updated until the Firefox 57 packages eventually return to the F26 testing repo after it is released upstream.The COPR will be removed at that point.
The Fedora Magazine article is going out tomorrow.
Thanks to everyone involved for the quick turn around on comments and editorial review.
Matt are you going to merge that branch back to master and F27 and continue from there?
Just want to make sure my scripts will point at your intended build source for the automated COPR updates.
_______________________________________________ devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx
