I understand what you’re saying and think I understand what you’re trying to do.
- It’s not possible to nest use of
rpmfrom withinrpm(lockbox asserted by rpm) - If you look at how Fedora installs itself from the bootable image –
- Create partition table on new OS device.
- Format partitions on new OS device
- Mount device’s partitions based at
/mnt/sysimage - Copy (extract) the required core OS files into
/mnt/sysimage - Bind current live kernel directories into ‘sysimage’
–mount --bind /proc /mnt/sysimage/proc
–mount --bind /sys /mnt/sysimage/sys
–mount --bind /dev /mnt/sysimage/dev - Execute necessary commands on the new target in its namespace
–chroot /mnt/sysimage <command(s)-or-script(s)> - Umount the filesystems
At this point, the target device is ready to be booted.
As you can see, completing configuration of the target OS installation is dependent on the critical kernel directories being present.
Regarding the packaging
I have a completely rewritten RPM package script set.
That package, like its current DEB counterpart, supports live-system, container (LXC or Docker), and Custom installation models.
I had previously offered it here in the forums.
There was insufficient interest to pursue further.
Without sufficient interest, the effort was placed on indefinite hold.
