package/forge: remove package

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>
Signed-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
This commit is contained in:
Thomas Perale
2025-08-29 12:33:32 +02:00
committed by Thomas Petazzoni
parent de970ee783
commit 37755d7275
6 changed files with 6 additions and 36 deletions

View File

@@ -1712,7 +1712,6 @@ F: package/erlang-p1-yconf/
F: package/erlang-p1-zlib/
F: package/erlang-stun/
F: package/erlang-xmpp/
F: package/forge/
F: package/nginx-dav-ext/
F: package/vis-network/
F: package/vuejs/