From mboxrd@z Thu Jan 1 00:00:00 1970 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on inbox.vuxu.org X-Spam-Level: ** X-Spam-Status: No, score=2.4 required=5.0 tests=DKIM_SIGNED,DKIM_VALID, DKIM_VALID_AU,FREEMAIL_FROM,HDRS_MISSP,T_SCC_BODY_TEXT_LINE autolearn=no autolearn_force=no version=3.4.4 Received: (qmail 26303 invoked from network); 16 Aug 2022 23:49:20 -0000 Received: from hurricane.the-brannons.com (2602:ff06:725:1:20::25) by inbox.vuxu.org with ESMTPUTF8; 16 Aug 2022 23:49:20 -0000 Received: from localhost.localdomain (localhost.localdomain [127.0.0.1]) by hurricane.the-brannons.com (OpenSMTPD) with ESMTP id a95f27d2 for ; Tue, 16 Aug 2022 16:49:15 -0700 (PDT) Received: from resqmta-a1p-077725.sys.comcast.net (resqmta-a1p-077725.sys.comcast.net [2001:558:fd01:2bb4::b]) by hurricane.the-brannons.com (OpenSMTPD) with ESMTPS id 2abcf2b0 (TLSv1.2:ECDHE-RSA-AES256-GCM-SHA384:256:NO) for ; Tue, 16 Aug 2022 16:49:08 -0700 (PDT) Received: from resomta-a1p-077051.sys.comcast.net ([96.103.145.229]) by resqmta-a1p-077725.sys.comcast.net with ESMTP id O023ozX1yaIELO6Aqo4fjQ; Tue, 16 Aug 2022 23:40:40 +0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=comcast.net; s=20190202a; t=1660693240; bh=+o3w3lfSFm571kt4KMirPnaHMx0WSgFL41/1ao9q9dM=; h=Received:Received:To:From:Reply-to:Subject:Date:Message-ID: Mime-Version:Content-Type; b=P16BT+VYjBdZqIyoEZcKdHO81spcS6234MZoTXkWWq/Ridb9DhvI9N58BHtzyOSL/ poXpvlpnkkjg/9RP4qwykCMzlnXDk19feGIct2B+wOltddA/go9uBjtLBbvXl6uwHZ vEQPaBE8DKPvtX4PuW/BCNlfACDX76Bhn0ogdmgXNKqIgkJWOCQbvQebvZ8Krxsgrf oUhKGZ7hdqXce09IRRyAOUd+B8fyjOhkoaBUabxtw0hTtlOSHq8GKqu51WcPeu72F/ JOzzHv/hb3u6ulNln+szLjDulmKhk6gfbdGhf8KHbww8eeM6r8E8hwnM57Aq+Z5rLm b+aRb+GcxCu+w== Received: from unknown ([IPv6:2601:408:c001:30:4259:70a1:3ded:2f47]) by resomta-a1p-077051.sys.comcast.net with ESMTPSA id O6AzobtAJ3omAO6B0ossxB; Tue, 16 Aug 2022 23:40:51 +0000 X-Xfinity-VMeta: sc=0.00;st=legit To:edbrowse-dev@edbrowse.org From: Karl Dahlke Reply-to: Karl Dahlke User-Agent: edbrowse/3.8.3+ Subject: can we quit patching quickjs? Date: Tue, 16 Aug 2022 19:40:49 -0400 Message-ID: <20220716194049.eklhad@comcast.net> X-BeenThere: edbrowse-dev@edbrowse.org List-Id: Edbrowse Development List Mime-Version: 1.0 Content-Type: multipart/mixed; boundary=nextpart-eb-903316 Content-Transfer-Encoding: 7bit This message is in MIME format. Since your mail reader does not understand this format, some or all of this message may not be legible. --nextpart-eb-903316 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: quoted-printable 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 --nextpart-eb-903316--