From: Efraim Flashner <efraim@flashner.co.il>
To: Ryan Prior <rprior@protonmail.com>
Cc: "43840@debbugs.gnu.org" <43840@debbugs.gnu.org>
Subject: [bug#43840] [PATCH] gnu: Add esbuild.
Date: Sun, 11 Oct 2020 13:28:53 +0300 [thread overview]
Message-ID: <20201011102853.GB1301@E5400> (raw)
In-Reply-To: <eRbjjbkvSfoIArq_dDiUdIJuEELuy9q0D1IjfscSbHRUxVzaKiPLRVlip0--bqGYaSiw_PDAhSrGLk-O0WJERF7MidM3bFZISAReIpsWG5A=@protonmail.com>
[-- Attachment #1: Type: text/plain, Size: 2239 bytes --]
On Thu, Oct 08, 2020 at 02:08:36AM +0000, Ryan Prior wrote:
> Hey Efraim, thank you for your comments!
>
> On Wednesday, October 7th, 2020 at 6:34 AM, Efraim Flashner <efraim@flashner.co.il> wrote:
>
> > There is an npm directory which is where the compiled binaries are
> > placed, there are a couple in the checked out repo.
>
> The compiled binaries might be placed there by the gnu-build-system, but the go-build-system does not put binaries there by itself. (Note that their make target explicitly specifies output directories.)
>
> I think our build totally ignores this directory, so it shouldn't matter whether we delete it, but if you think removing the unneeded directory improves the package I'll update the patch with a snippet.
It's important to not ship any precompiled binaries so go ahead and
remove them in a snippet.
> > Is it worth trying to run some of the test suite? I see there are a
> > couple of 'make check' type targets in the Makefile at the root of the
> > repository and currently there are none run during the build.
>
> It would be nice to run their tests, but the test system currently assumes network access to install some various JavaScript dependencies using npm. We might patch the test system and vendor in the deps (used only for testing,) what do you think?
>
I was able to run some of the test suite with the following arguments section:
(arguments
'(#:import-path "github.com/evanw/esbuild/cmd/esbuild"
#:unpack-path "github.com/evanw/esbuild"
#:phases
(modify-phases %standard-phases
(replace 'check
(lambda* (#:key tests? unpack-path #:allow-other-keys)
(if tests?
(with-directory-excursion (string-append "src/" unpack-path)
(invoke "make" "test-go"))
#t))))))
Unfortunately it also depends on github.com/kylelemons/godebug/diff, but
it doesn't look like it has any dependants. With that added as a
native-input I think it's ready.
> Ryan
Thanks
--
Efraim Flashner <efraim@flashner.co.il> אפרים פלשנר
GPG key = A28B F40C 3E55 1372 662D 14F7 41AA E7DC CA3D 8351
Confidentiality cannot be guaranteed on emails sent or received unencrypted
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2020-10-11 10:30 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-07 2:31 [bug#43840] [PATCH] gnu: Add esbuild Ryan Prior via Guix-patches via
2020-10-07 6:34 ` Efraim Flashner
2020-10-08 2:08 ` Ryan Prior via Guix-patches via
2020-10-11 10:28 ` Efraim Flashner [this message]
2020-10-11 16:15 ` Ryan Prior via Guix-patches via
2020-10-11 16:16 ` [bug#43840] [PATCH 1/2] gnu: Add go-github-com-kylelemons-godebug Ryan Prior via Guix-patches via
2020-10-11 16:16 ` [bug#43840] [PATCH 2/2] gnu: Add esbuild Ryan Prior via Guix-patches via
2020-10-12 6:41 ` bug#43840: " Efraim Flashner
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:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20201011102853.GB1301@E5400 \
--to=efraim@flashner.co.il \
--cc=43840@debbugs.gnu.org \
--cc=rprior@protonmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* 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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).