Paul Spooren 15b7994c01 imagebuilder: cleanup package inclusion
Previously three different ways to include packages in an ImageBuilder
existed:

* buildbot: include libc, kernel (and base-files) in $(IB_LDIR)
* not buildbot, standalone: include all packages in ./packages/
* not buildbot, not standalone: include libc, kernel (and base-files) in
  ./packages/

First of, the separation between *buildbot* and *not buildbot, not
standalone* is not required, we can just always copy packages to
./packages instead of ever using the special place $(IB_LDIR).
Doing so drops the need to handle the extra case and also allows to
clean up the OPKG package installation, which no longer requries the
`firstword` logic, things are now always at ./packages.

Signed-off-by: Paul Spooren <mail@aparcar.org>
2024-11-09 16:46:41 +01:00
..

./packages folder

Add .ipk packages to this folder will allow the ImageBuilder to install them.

For more complex setups consider adding a custom feed containing packages.

src custom file:///path/to/packages

Whenever the ImageBuilder builds a firmware image this folder will be reloaded and a new package index created. In case signature checks are enabled the ./packages/Packages index will be signed with a locally generated key pair.