Le ven. 17 janv. 2025 à 13:47, Sebastian Humenda <shume...@gmx.de> a écrit :
> Hi > > Jérémy Lal schrieb am 17.01.2025, 12:23 +0100: > >Le jeu. 16 janv. 2025 à 19:20, Sebastian Humenda <shume...@gmx.de> a > écrit : > > > >> I recall that upstream of Edbrowse wasn't so intrested in switching to > >> quickjs-ng. For me, it's mostly a matter of actually trying edbrowse > with > >> quickjs-ng, as quickjs was packed *because of* edbrowse. I do lack the > time > >> ATM, so if you'd be willing to take a look whether this works, I'd > >> appreciate > > > >I've pushed a Draft PR to edbrowse. > > I'll take a look. > I've built edbrowse with quickjs-ng, and opened a web page with it. However I don't know how to test the js part. > > >I propose to maintain quickjs. I'm going to use it with nginx's njs. > >It makes sense to me to change its team maintenance to > >pkg-javascript-devel, or even simply to debian group. > > I'd like to stay uploader Ok > I'd follow your suggestion, pkg-javascript sounds > reasonable, but I won't be able to follow the team's development along. > It's okay to not subscribe to pkg-javascript-devel. What steps are required from my side? > I have granted you access as a maintainer to https://salsa.debian.org/js-team/quickjs-ng You can review the changes I made there (I may have missed some issues). You just need to use that repository. I noticed that quickjs-ng is not yet usable as a shared library. https://github.com/quickjs-ng/quickjs/issues/675 gives hope, though. Jérémy
