From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Thomas Perale via buildroot <buildroot@buildroot.org>
Cc: Thomas Perale <thomas.perale@mind.be>,
Thomas Claveirole <thomas.claveirole@green-communications.fr>,
Simon Dawson <spdawson@gmail.com>,
Johan Oudinet <johan.oudinet@gmail.com>
Subject: Re: [Buildroot] [PATCH 01/15] docs/migrating.adoc: document static JS library
Date: Thu, 1 Jan 2026 22:55:18 +0100 [thread overview]
Message-ID: <20260101225518.501f73ff@windsurf> (raw)
In-Reply-To: <20250829103340.158873-1-thomas.perale@mind.be>
On Fri, 29 Aug 2025 12:33:26 +0200
Thomas Perale via buildroot <buildroot@buildroot.org> wrote:
> This patch adds information on how to provides static JS libraries in
> Buildroot with the release of the 2025.08.x version.
>
> Because the way JavaScript project development is working the chances that your
> project is using the same version of the buildroot package, and you provide
> this library from `/var/www` to your users is actually really low ...
>
> If you want to bundle JavaScript libraries in your project you should probably
> either use a cdn, handle the package version and location of your choice in
> your external or overlay, or just bundle it in your assets from a NPM workflow
> to benefit from some minifications from your bundler.
>
> Historically many of those JavaScript libraries were added in the 2010 eras
> where it could make sense for them to be part of Buildroot.
>
> Most of them are also way outdated/not maintained.
>
> For more informations see https://elinux.org/Buildroot:DeveloperDaysELCE2025
>
> Signed-off-by: Thomas Perale <thomas.perale@mind.be>
> ---
> docs/manual/migrating.adoc | 11 +++++++++++
> 1 file changed, 11 insertions(+)
Thanks, whole series applied!
Thomas
--
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
prev parent reply other threads:[~2026-01-01 21:55 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-29 10:33 [Buildroot] [PATCH 01/15] docs/migrating.adoc: document static JS library Thomas Perale via buildroot
2025-08-29 10:33 ` [Buildroot] [PATCH 02/15] package/bootstrap: remove package Thomas Perale via buildroot
2025-08-29 10:33 ` [Buildroot] [PATCH 03/15] package/chartjs: " Thomas Perale via buildroot
2025-08-29 10:33 ` [Buildroot] [PATCH 04/15] package/datatables{, -buttons, -fixedcolumns, -responsive}: " Thomas Perale via buildroot
2025-08-29 10:33 ` [Buildroot] [PATCH 05/15] package/explorercanvas: " Thomas Perale via buildroot
2025-08-29 10:33 ` [Buildroot] [PATCH 06/15] package/flot: " Thomas Perale via buildroot
2025-08-29 10:33 ` [Buildroot] [PATCH 07/15] package/forge: " Thomas Perale via buildroot
2025-08-29 10:33 ` [Buildroot] [PATCH 08/15] package/jquery: " Thomas Perale via buildroot
2025-08-29 10:33 ` [Buildroot] [PATCH 09/15] package/json-javascript: " Thomas Perale via buildroot
2025-08-29 10:33 ` [Buildroot] [PATCH 10/15] package/jszip: " Thomas Perale via buildroot
2025-08-29 10:33 ` [Buildroot] [PATCH 11/15] package/openlayers: " Thomas Perale via buildroot
2025-08-29 10:33 ` [Buildroot] [PATCH 12/15] package/vis-network: " Thomas Perale via buildroot
2025-08-29 10:33 ` [Buildroot] [PATCH 13/15] package/vuejs: " Thomas Perale via buildroot
2025-08-29 10:33 ` [Buildroot] [PATCH 14/15] package/jsmin: " Thomas Perale via buildroot
2025-08-29 10:33 ` [Buildroot] [PATCH 15/15] package/duktape: move submenu Thomas Perale via buildroot
2025-08-29 12:08 ` Edgar Bonet via buildroot
2026-01-01 21:55 ` Thomas Petazzoni via buildroot [this message]
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=20260101225518.501f73ff@windsurf \
--to=buildroot@buildroot.org \
--cc=johan.oudinet@gmail.com \
--cc=spdawson@gmail.com \
--cc=thomas.claveirole@green-communications.fr \
--cc=thomas.perale@mind.be \
--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