edbrowse-dev - development list for edbrowse
 help / color / mirror / Atom feed
From: Sebastian Humenda <shumenda@gmx.de>
To: edbrowse-dev@edbrowse.org
Subject: QuickJS and maintenance
Date: Wed, 8 Feb 2023 10:32:46 +0100	[thread overview]
Message-ID: <Y+NsPuKApVhdHG2g@kraftkrust> (raw)

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

Hi all

I have prepared a packaged version of QuickJS for Debian that is a dependency
of Edbrowse. However, during that process the question got raised whether such a
security-sensitive package would be appropriate to package in Debian. The main
point is that this puts additional burden on the Debian security team and it
seems that QuickJS is not the most actively maintained project.

Hard specific are the bindings of Edbrowse to QuickJS and is it feasible to
switch to something else? To me, Duktape comes to mind. It looks slightly more
maintained and is already in Debian.


[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

             reply	other threads:[~2023-02-08  9:38 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-08  9:32 Sebastian Humenda [this message]
2023-02-08 10:33 ` Karl Dahlke
2023-02-09  8:13   ` Adam Thompson
2023-02-09  9:48     ` Sebastian Humenda
2023-02-11  8:10       ` Adam Thompson
2023-02-11  9:56         ` Sebastian Humenda
2023-02-11 10:32           ` Karl Dahlke
2023-02-12  7:39             ` Sebastian Humenda
2023-02-12 18:54               ` Adam Thompson

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=Y+NsPuKApVhdHG2g@kraftkrust \
    --to=shumenda@gmx.de \
    --cc=edbrowse-dev@edbrowse.org \


* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
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).