This commit overhauls the rootfs package to create a regular package
for the root filesystem instead of creating a packaged squashfs. The
release packages then use pkg2sqfs to turn it into a squashfs image.
Signed-off-by: David Oberhollenzer <goliath@infraroot.at>
- drop the 3 suffix, they contain generic firmware
- rename the "firwmare" package to "vc" as it contains stuff for the
video core
Signed-off-by: David Oberhollenzer <goliath@infraroot.at>
- 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>
This commit renames the release packages so they all produce a single
package named "release", creates a preference listing from the
PREFERED_PROVIDER array and lets `pkg buildstrategy` decide what package
to build.
Signed-off-by: David Oberhollenzer <goliath@infraroot.at>
Same process as for the build dir. We have one intermediate deploy directory
that the packaes installs it self to, then we package the contents, finally
we nuke the build and deploy directory before starting with the next package.
Signed-off-by: David Oberhollenzer <goliath@infraroot.at>
The initial ram disk does that for us (with the propper permissions
in the case of Qemu).
Signed-off-by: David Oberhollenzer <david.oberhollenzer@tele2.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>
Instead of having an overlay mounted /root in the root filesystem,
move it to the other user directories, i.e. /usr/root.
We then overlay mount the entire /usr directory. This still allows
us to mount /usr from somewhere else if we wish, but cleans
up/simplifies the filesystem for now and implements some default
management of general user directories.
Signed-off-by: David Oberhollenzer <david.oberhollenzer@tele2.at>
Use $PKGBUILDDIR for building packages. Delete it again after
the deploy is done. If the build fails, the script aborts and it
is kept. If the build and deploy pass, there is no reason to keep
it around.
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>
- Dedicate home directory for root user (classic /root)
- Root homedirectory is overlay mounted
- Allows us to have an empty user directory that we directly
mount, i.e. without using overlay fs
Signed-off-by: David Oberhollenzer <david.oberhollenzer@tele2.at>
