Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Claveirole <thomas.claveirole@green-communications.fr>
To: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
Cc: Daniel Price <daniel.price@gmail.com>,
	Martin Bark <martin@barkynet.com>,
	Johan Oudinet <johan.oudinet@gmail.com>,
	buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH 1/2] package/nodejs: introduce BR2_PACKAGE_HOST_NODEJS_COREPACK
Date: Mon, 26 Sep 2022 11:04:38 +0200	[thread overview]
Message-ID: <3124822.5fSG56mABF@harderbit> (raw)
In-Reply-To: <20220925215340.43f64019@windsurf>


[-- Attachment #1.1: Type: text/plain, Size: 1090 bytes --]

> Replying to myself: "corepack enable" does not download stuff. [...]

It sounds good indeed.  To be honest, all this Node packaging gets a bit over 
my head and I am not sure how it works exactly (the whole JavaScript packaging 
ecosystem just looks crazy to me).  I usually just use compiled JavaScript 
files and almost never compile them myself.

I thought that using host-nodejs to compile JavaScript packages was a new 
Buildroot policy, but apparently according to [1] and [2] we prefer to stick 
to precompiled JavaScript files?  If so, I will send a v2 patch for the vuejs 
package (... when I find some time.)

[1] https://lore.kernel.org/buildroot/20220919114617.67d80b53@windsurf/
[2] https://lore.kernel.org/buildroot/20220924170516.4a0323dc@windsurf/

(As for my opinion, should it have any relevance: I also prefer that Buildroot 
relies on pre-compiled files, at least as long as it cannot do some vendoring 
for Node packages.  Downloading stuff outside of Buildroot's download system 
is quite annoying.)

-- 
Thomas Claveirole <thomas.claveirole@green-communications.fr>

[-- Attachment #1.2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

[-- Attachment #2: Type: text/plain, Size: 150 bytes --]

_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

  reply	other threads:[~2022-09-26  9:04 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-13 17:40 [Buildroot] [PATCH 0/2] Update host-nodejs and build vuejs from source Thomas Claveirole
2022-09-13 17:40 ` [Buildroot] [PATCH 1/2] package/nodejs: introduce BR2_PACKAGE_HOST_NODEJS_COREPACK Thomas Claveirole
2022-09-25 19:47   ` Thomas Petazzoni
2022-09-25 19:53     ` Thomas Petazzoni
2022-09-26  9:04       ` Thomas Claveirole [this message]
2022-09-26 10:01         ` Thomas Petazzoni
2022-09-26 10:17           ` Johan Oudinet
2022-09-26 10:24             ` Thomas Petazzoni
2023-04-16 19:48   ` Yann E. MORIN
2022-09-13 17:40 ` [Buildroot] [PATCH 2/2] package/vuejs: bump to version 3.2.39 Thomas Claveirole

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

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

  git send-email \
    --in-reply-to=3124822.5fSG56mABF@harderbit \
    --to=thomas.claveirole@green-communications.fr \
    --cc=buildroot@buildroot.org \
    --cc=daniel.price@gmail.com \
    --cc=johan.oudinet@gmail.com \
    --cc=martin@barkynet.com \
    --cc=thomas.petazzoni@bootlin.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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox