Running zopen-promote to promote an environment from one area to another, the contents of $ZOPEN_ROOTS/var/cache/zopen are also migrated over. These are unnecessary (for a normal, non-tooling promote) as users cannot reinstall the pax files so take up space in the new area as well as take time to process
Note there could be an argument for users maybe wanting to directly install the pax into their environment, but re-downloading from GH or running their own zopen environment would be the more sensible option.
The workaround is to do a zopen clean -c prior to running the promote, but then the cache might be cleared when it was actually required so promote shouldn't copy the files...
Running zopen-promote to promote an environment from one area to another, the contents of $ZOPEN_ROOTS/var/cache/zopen are also migrated over. These are unnecessary (for a normal, non-tooling promote) as users cannot reinstall the pax files so take up space in the new area as well as take time to process Note there could be an argument for users maybe wanting to directly install the pax into their environment, but re-downloading from GH or running their own zopen environment would be the more sensible option. The workaround is to do a zopen clean -c prior to running the promote, but then the cache might be cleared when it was actually required so promote shouldn't copy the files...