mirror of
https://gitlab.com/buildroot.org/buildroot.git
synced 2026-08-01 21:23:51 -09:00
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:
committed by
Thomas Petazzoni
parent
de970ee783
commit
37755d7275
@@ -146,6 +146,12 @@ endif
|
||||
|
||||
comment "Legacy options removed in 2026.02"
|
||||
|
||||
config BR2_PACKAGE_FORGE
|
||||
bool "forge has been removed"
|
||||
select BR2_LEGACY
|
||||
help
|
||||
JS libraries are no longer part of Buildroot packages.
|
||||
|
||||
config BR2_PACKAGE_FLOT
|
||||
bool "flot has been removed"
|
||||
select BR2_LEGACY
|
||||
|
||||
Reference in New Issue
Block a user