The Custom Installer Builder creates and stores a new archive file for each customized installer created. This not only consumes disk space on the CIB machine (see #1008), it also means that the version of Seattle that was current when the installer was created will remain built into that installer.
Maybe this is not a big problem as each install will go and update itself, but I would prefer to ship up-to-date versions from the server right away to minimize the scope of potential problems (especially ones in the updater).
It shouldn't be hard to do either: make_base_installers.py would need to include logic to just remove the existing archive files (but not vesselinfos!) from the Custom Installer Builder's html/static/installers/RANDOM_HASH directories.
If that route is taken, this would be a great newcomer ticket.
The Custom Installer Builder creates and stores a new archive file for each customized installer created. This not only consumes disk space on the CIB machine (see #1008), it also means that the version of Seattle that was current when the installer was created will remain built into that installer.
Maybe this is not a big problem as each install will go and update itself, but I would prefer to ship up-to-date versions from the server right away to minimize the scope of potential problems (especially ones in the updater).
It shouldn't be hard to do either:
make_base_installers.pywould need to include logic to just remove the existing archive files (but notvesselinfos!) from the Custom Installer Builder'shtml/static/installers/RANDOM_HASHdirectories.If that route is taken, this would be a great newcomer ticket.