- All linux packages generate "linux" and "linux-modules"
- Preference mechanism is used to select the right source package
- Rootfs depends on "linux-modules" to install the selected kernels
modules into the squashfs image
- The release pacakge depends on "linux" to install the appropriate
kernel to the boot partition
Signed-off-by: David Oberhollenzer <goliath@infraroot.at>
- rewrite the rootfs_files.txt listings to the format used by pkg
- create package files from each package
- use "pkg install" to manage installation of packages and dependencies
into the rootfs and initrd staging dirs
Signed-off-by: David Oberhollenzer <goliath@infraroot.at>
Just install the kernel package to the rootfs /boot directory and add a step
to the rootfs package to move /boot data out of the squasfs image.
Add linux package as regular dependency to the rootfs.
Signed-off-by: David Oberhollenzer <david.oberhollenzer@tele2.at>
Crunch project websites and try to find the latest version for each
package without having to do the work manually.
Signed-off-by: David Oberhollenzer <david.oberhollenzer@tele2.at>
- build needs a pair of product and board name
- some products can only be built for some boards
- Config files in product/<name> directory override those in board/<name>
- For some config files, like LDPATH or ROOTFS, the files are merged
- product/common provides defaults
Add default config for various services:
- Add default config for unbound
- Add default config for dnsmasq
Signed-off-by: David Oberhollenzer <david.oberhollenzer@tele2.at>
- Use shipped device tree binaries instead of our own
- Install kernel + rootfs to $OS_RELEASE subdirectory
Signed-off-by: David Oberhollenzer <david.oberhollenzer@tele2.at>
Instead of having a "depends" file with a list of packages, add a
"DEPENDS" variable to the build script.
Generate the rootfs dependencies from a config file stored in the
cfg directory.
Signed-off-by: David Oberhollenzer <david.oberhollenzer@tele2.at>
David Oberhollenzer
David Oberhollenzer