edbrowse-dev - development list for edbrowse
 help / color / mirror / Atom feed
* can we quit patching quickjs?
@ 2022-08-16 23:40 Karl Dahlke
  2022-08-17  0:28 ` Dominique Martinet
  0 siblings, 1 reply; 3+ messages in thread
From: Karl Dahlke @ 2022-08-16 23:40 UTC (permalink / raw)
  To: edbrowse-dev

[-- Attachment #1: Type: text/plain, Size: 936 bytes --]

Folks, I had a clever, and somewhat frightening, and somewhat ugly thought, but no uglier that patching and building quickjs ourselves.
I can enqueue a job manually, just as promise does, then scan the runtime structure to see what has changed.
This is, hopefully, the location of the jobs queue.
The commit is 42d5b695989a9dc92dc66a7de6f92176d2e0a0de
Look at it as a patch file and see what I did.
I encourage you brave souls to try it out.
If we all decide it works, and is safe, then we can delete tools/quickjobfixup, and remove all  those instructions about patching and building quick from source,
and just link to the quick package, if one is distributed and available.
Of course if there is no quick package, and there often isn't, the user or the package manager can still build quick from source, but he doesn't have to patch it.

I don't know why I didn't think of this sooner.

Comments welcome.

Karl Dahlke

^ permalink raw reply	[flat|nested] 3+ messages in thread

end of thread, other threads:[~2022-08-17  0:51 UTC | newest]

Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2022-08-16 23:40 can we quit patching quickjs? Karl Dahlke
2022-08-17  0:28 ` Dominique Martinet
2022-08-17  0:43   ` Karl Dahlke

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).