On 6/19/20 4:11 PM, Ken Moffat via blfs-dev wrote:
Guys,
at the end of this month firefox will move to the next ESR series,
78. Surprisingly, it has not required a newer version of rust since
we last updated that, so the firefox part can just drop in.
We are currently using latest firefox-68 to provide spidermonkey
(JS), because both books need that for polkit, and we at last have
a version of polkit which will use JS68.
With firefox-78, a lot has changed. From the 'Help' screen of
78.0b8 I can see: New RegExp engine in SpiderMonkey, adding support
for the dotAll flag, Unicode escape sequences, lookbehind
references, and named captures.
That no doubt explains why the spidermonkey code now pulls in some
rust code. I gave that combination a trial a week or so ago, and
after ensuring that rustc was present the build failed miserably,
it looked like C++ scope errors.
So, I'm proposing to keep JS68 in the book, and therefore separate
it from firefox. As to whether newer versions of 68 will be worth
the effort of updating for this (I think there might be two more), I
have no idea.
Once firefox-78 is in, it will use python3. JS68 is still python2 -
last December xry111 had a patch to let JS68 use python3. I
remember building that on my py3 system, but since the polkit I was
using did not use JS68 and I was not able to address that, I had to
drop the polkit chain (JS68, polkit, elogind, rootless X). But
since then we have dropped the cut-down JS68 from fdo and moved to
using the JS shipped in firefox. Maybe we should reconsider that ?
I'm not 100% sure I understand, but can't we use FF68 source for js68
and polkit and use FF78 separately?
-- Bruce
--
http://lists.linuxfromscratch.org/listinfo/blfs-dev
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page
