I know Seamonkey gets security updates to the newest firefox esr, but does Seamonkey get web engine updates, Like for the newest html and JS features? If not, could you use UXP to keep it updated?

hit'n'run

and the shortest answer is probably really "that's what's being done already". Also they forgot to mention CSS

"redhat jira"

that's fun... But at this rate I'd not be surprised if Mozilla themselves abandoned bugzilla :-\

Good morning njsg and frg_Away

nsITobin hi

github.com/lah7/gtk3-classic/tree/master i deff need to apply all these patches to gtk3 once my lfs is up and going

frg_Away: so bugzilla.mozilla.org/1441651 looks like the next item on the vs2022 list I think

my skills are still rusty as hell.. this is NOT acceptable cause rust never is lol

trying next but currently the wip branch does not like gcc. If VS2022 does not like part 4 from bug 1530937 I need someone with c++ skills who can unbreak the mozilla mess.

frg_Away: at some point you will have to switch the codebase to clang only

mozilla stopped considering vs2022 as a compiler around this time

I very much dislike this

i do too

I know

i beleive the predominate system compiler should be responsible.. msvc for winders gcc for anything unix but not mac

heh that old define

clang is ok but I want a second one working in case of dumps and errors. Not the first time a compiler failed to produce bad code.

^and produced

this is why clang is unacceptable

because it does not generate its self.

thus it is an invalid system compiler in my opinion

gcc compiles its self

and instead of just needing gcc and autohell you also need cmake which has even more dependancies

it is basically why I have rejected RPM package management for my thing going forward .. system components shouldn't need too many high level dependancies and requirements because THEY are the basis upon more complex stuff is built

frg_Away: which gcc version are you attempting to use for 1530937

well clang > 14 currently can not build the cross compiled macOS version. Crashes when started.

gcc 9

from CentOS 7

is our current short .. "short" term goal to get to 68 eq functionality then take stock?

I try to get some more parser stuff in to be able to backport fields. Also need to rebase the current optional chaining and regexp stuff which is currently not in.

I think 68 is a good middle point to try.

if I had the time at the moment I'd start investigating ESR68 .. and seeing if the war on xbl can be reversed.. because I think it can and if so Thunderbird maintained rdf far longer than mozilla did .. if most extensions are long abandoned and busted than aside from content blockers and privacy nonsense the extension system and definition is up to you and if it is a factor in doing something.

CoordinatorTobin i left most of the xpconect stuff out and only did the needed things for compartment to realm. Need to review it later but so far it seems to work fine with end of 67. Unfortunatetely they added about a 1000 patches in 68. Seems to be one of the last big change releases before the layoffs and slow down.

yeah i thought the same thing

welcome back

wonder if this firefox 68 will build successfully

nope

oh rust issues

If you build the real esr68 you need old rust.

yeah and I can't easily get that on linux.. another reason rust is evil

CaptaionTobin rustup works for me too there.

got the command handy?

Need to re open the vm. stay tuned

export PATH="/mnt/linuxdata/seamonkey/linux/nasm:$HOME/.cargo/bin:$PATH"

rustup default 1.73.0-x86_64-unknown-linux-gnu

removed system rust and installed rustup and am running rustup-init

installing 1.73

cd /binoc/workstation/projects/newcode/esr68

err

error: proc-macro derive panicked

1.73 is too new

1.34 seems to be it in 68

yupp bug 1536543

5:03.58 error: failed to run custom build command for `style v0.0.1 (/binoc/workstation/projects/newcode/esr68/servo/components/style)`

5:03.58 process didn't exit successfully: `/binoc/workstation/projects/newcode/esr68/obj-x86_64-pc-linux-gnu/release/build/style-215d39610807c9c7/build-script-build` (exit code: 101)

with 1.34

what a robust and dependable and safe language so safe you can't even reliably compile it to even run it.. can't get more safe than that!

been there seen it

trying to get stylo to work for some time now

I was in a lunar trench lobbing insults at people rather than accepting rust's existance remember..

so i get all the nastyness all at once

instead of trickled out over years

I give up .. for now.. Obviously building on here isn't gonna work. I will have to select a period system and that is way more work than is warrented for a quick experiment

GitLab now enforces expiry dates on tokens that originally had no set expiration date. Those tokens were given an expiration date of one year later. Please review your personal access tokens, project access tokens and group access tokens to ensure you are aware of upcoming expirations.

wonder when github will do the same thing

ContributorTobin welcome the the club of real life rust users :)

it's gross

there now that that all works .. and cli is fixed i can move it back onto the web ibb.co/JjKfQ73

get those modules rewritten so they actually work

and components

sup njsg