Changeset 8d219de for xsoft/graphweb

Timestamp:

12/13/2022 07:47:32 PM (18 months ago)

Author:

Ken Moffat <ken@…>

Branches:

11.3, 12.0, 12.1, kea, ken/TL2024, ken/inkscape-core-mods, ken/tuningfonts, lazarus, lxqt, plabs/newcss, plabs/python-mods, python3.11, qt5new, rahul/power-profiles-daemon, renodr/vulkan-addition, trunk, xry111/llvm18, xry111/xf86-video-removal

Children:

1514851

Parents:

48771ae

Message:

Updates:

firefox-102.6.0,
js-102.6.0.

Measured on AMD 3400G using linux-6.0.12, and only 4 cores online
for JS, sizes and timings on other machines differ slightly.

File:

• xsoft/graphweb/firefox.xml (modified) (1 diff)

xsoft/graphweb/firefox.xml

@@ -7 +7 @@
   <!ENTITY firefox-download-http "&mozilla-http;/firefox/releases/&firefox-version;esr/source/firefox-&firefox-version;esr.source.tar.xz">
   <!ENTITY firefox-download-ftp  " ">
-  <!ENTITY firefox-md5sum        "3b3e610898ccda554519f744e634c50c">
+  <!ENTITY firefox-md5sum        "9fe60d1991b9344ebfd80592aff2bfa9">
   <!ENTITY firefox-size          "457 MB">
   <!-- NB with stylo, much of the build uses rust, and therefore cargo files.
     But the extra cached cargo files, if any, seem to be minimal -->
-  <!ENTITY firefox-buildsize     "7.1 GB (197 MB installed) without tests">
+  <!ENTITY firefox-buildsize     "7.1 GB (199 MB installed) without tests">
   <!-- editors: with ff63 and rust-1.29, ./mach build -j4 is probably the
    most practical way to get a timing on a machine with more cores, if taking
    cores offline is not practical. If in doubt, round up -->
-  <!ENTITY firefox-time          "20 SBU using -j4, without tests">
+  <!ENTITY firefox-time          "21 SBU using -j4, without tests">
 ]>