Looking through the manifest for what happens to packages built using kaem, all but one of them either get rebuilt using bash (e.g. bzip2), replaced with a newer version (e.g. bash itself), or only needed early in the bootstrap, being replaced by completely different software (e.g. mes). The one exception is gzip, which is carried forward as an unpackaged binary all the way till the very end of the process.
This is obviously less than ideal. It would be nice if gzip was either rebuilt or upgraded at some point in the bootstrap.
Looking through the manifest for what happens to packages built using kaem, all but one of them either get rebuilt using bash (e.g. bzip2), replaced with a newer version (e.g. bash itself), or only needed early in the bootstrap, being replaced by completely different software (e.g. mes). The one exception is gzip, which is carried forward as an unpackaged binary all the way till the very end of the process.
This is obviously less than ideal. It would be nice if gzip was either rebuilt or upgraded at some point in the bootstrap.