You are not logged in.
As with new version of archiso, customize_airootfs.sh will be deprecated, what is alternative to perform administrative tasks?
Last edited by AashishMann (2020-09-03 17:43:35)
Offline
The removal of customize_airootfs.sh will not happen just yet. It's unfortunately still required to run locale-gen.
As for the alternative, there is not direct alternative, the actions just have to be performed in a different way. E.g. services can be enabled by creating the symlinks and users can be created by creating /etc/passwd, /etc/shadow, /etc/group and /etc/gshadow.
All this is in effort to make the ISO more reproducible.
Offline
the actions just have to be performed in a different way. E.g. services can be enabled by creating the symlinks and users can be created by creating /etc/passwd, /etc/shadow, /etc/group and /etc/gshadow.
Thanks, this solves most of my problems, but is there a way to prevent overwriting of custom files which are not specified as backup files, by packages installed, for example kodi config files in /usr/share
Offline
The removal of customize_airootfs.sh will not happen just yet. It's unfortunately still required to run locale-gen.
As for the alternative, there is not direct alternative, the actions just have to be performed in a different way. E.g. services can be enabled by creating the symlinks and users can be created by creating /etc/passwd, /etc/shadow, /etc/group and /etc/gshadow.
All this is in effort to make the ISO more reproducible.
This is orthogonal to being reproducible. Adding a file to airootfs before building doesn't produce different output from copying it in customize_airootfs.sh, the *correct* approach is sed because your PR makes the file fall out of sync with the supported locales.
Managing AUR repos The Right Way -- aurpublish (now a standalone tool)
Offline
Thanks, this solves most of my problems, but is there a way to prevent overwriting of custom files which are not specified as backup files, by packages installed, for example kodi config files in /usr/share
/usr/share/ is considered package manager territory, so messing with it is generally advised against, but that's beside the point. For kodi, you could place custom configuration in airootfs/home/username/.kodi/userdata/ .
This is orthogonal to being reproducible. Adding a file to airootfs before building doesn't produce different output from copying it in customize_airootfs.sh, the *correct* approach is sed because your PR makes the file fall out of sync with the supported locales.
Actually, I mixed up a few things. It was not about being reproducible, but about having declarative profiles. Or maybe both...
Last edited by nl6720 (2020-09-03 16:23:55)
Offline
For kodi, you could place custom configuration in airootfs/home/username/.kodi/userdata/ .
Yes, I exactly did this, I have managed to completely shift out of dependency on customize_airootfs.sh, it just took some extra steps, but overall it did declutter my build process.
Solved.
Offline