Improve UX for flatpaks

[hayamahamed]

The current bluebuild installs flatpaks at runtime, requiring connectivity after installation.

But upstream fedora does differently, it puts the flatpak in a directory of the iso, installs from it, rewrite the remote, and delete it.

I wonder is it possible to make the flatpak module get the flatpak work just as same so, users have a better experience.

[xynydev]

BlueBuild is currently behind on the ISO front, yeah. We don't really have flatpak bundling in ISOs implemented, but also, the whole ISO building thing built into the CLI is outdated and will be replaced by @gmpinder in the future.

The modules however, have nothing to do with ISOs. The main thing that BlueBuild can build is OCI container images that bootc can install as full bare-metal Linux systems. The modules are part of this build process. The only ways to install flatpaks inside a custom image like this is how we are currently doing it, or another more complicated method that leaves the flatpaks read-only on the booted system. We're currently using this method to better facilitate flatpak management on booted systems without having to tinker with the image, but both could be considered in the future possibly maybe.

But in general, ISOs are only a convenience feature and you don't have to use BlueBuild CLI to build them. That's right, you can use whatever compatible ISO builder you like, some of which may support adding flatpaks in the ISO image! Many possible options are here: blue-build/cli#613

[hayamahamed]

First, thank you for your time & detailed explanation <3.

I guess i should inject a start script at post build step.