From: "Yann E. MORIN" <yann.morin.1998@free.fr>
To: Johan Oudinet <johan.oudinet@gmail.com>
Cc: buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH] package/forge: new package
Date: Fri, 26 Aug 2022 23:07:12 +0200 [thread overview]
Message-ID: <20220826210712.GE37358@scaer> (raw)
In-Reply-To: <CAJtjsKZtjXnqki4+yPdkdLNcVa+4kOfmybk-_5yxA8497r31-Q@mail.gmail.com>
Johan, All,
On 2022-08-26 16:11 +0200, Johan Oudinet spake thusly:
> On Mon, Aug 22, 2022 at 4:12 PM Yann E. MORIN <yann.morin.1998@free.fr> wrote:
> > Instead, you should grab the sources from th github repo, have the
> > package depend on host-nodejes, and build the pacakge with $(NPM) build.
>
> Thanks for the suggestion. I didn't know we could do that in recent
> versions of buildroot.
> It is indeed a much cleaner way to handle npm packages, even though I
> don't like the BUILD commands to download the dependencies.
Yeah, this is indeed not nice, but there is nt much we can do for now.
If we get a good nderstanding of how npm-based pacages work, then we can
look into introducing a download post-processing script, like we have
for go and cargo, where the vendoring is done as part of the download
step.
But I don't think I could spot a similar (mis)feature in npm...
Regards,
Yann E. MORIN.
> I've uploaded a new version with your suggestions.
>
> Best regards,
> --
> Johan
> _______________________________________________
> buildroot mailing list
> buildroot@buildroot.org
> https://lists.buildroot.org/mailman/listinfo/buildroot
--
.-----------------.--------------------.------------------.--------------------.
| Yann E. MORIN | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
| +33 662 376 056 | Software Designer | \ / CAMPAIGN | ___ |
| +33 561 099 427 `------------.-------: X AGAINST | \e/ There is no |
| http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL | v conspiracy. |
'------------------------------^-------^------------------^--------------------'
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2022-08-26 21:07 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-22 16:07 [Buildroot] [PATCH] package/forge: new package Johan Oudinet
2022-08-22 14:12 ` Yann E. MORIN
2022-08-26 14:11 ` Johan Oudinet
2022-08-26 21:07 ` Yann E. MORIN [this message]
2022-08-26 13:08 ` [Buildroot] [PATCH v2] " Johan Oudinet
2022-08-27 8:47 ` Yann E. MORIN
2022-08-28 8:06 ` Thomas Petazzoni via buildroot
2022-08-28 8:35 ` Yann E. MORIN
2022-09-01 15:43 ` Johan Oudinet
2022-09-24 15:05 ` Thomas Petazzoni
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=20220826210712.GE37358@scaer \
--to=yann.morin.1998@free.fr \
--cc=buildroot@buildroot.org \
--cc=johan.oudinet@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.