While developing a project, an author will likely generate lots of latex-images and similar that don't end up in the final project. On every build that generates assets, we cache these images. That makes rebuilding fast, but as soon as an image is abandoned, it will just sit in the cache forever.
A pretext cleanup function could get the hash of every cached image and save only those that are still in the document.
Related to #1218, but not automatic. The cleanup command should also prune the logs (maybe completely), depending on what the automatic policy is.
While developing a project, an author will likely generate lots of latex-images and similar that don't end up in the final project. On every build that generates assets, we cache these images. That makes rebuilding fast, but as soon as an image is abandoned, it will just sit in the cache forever.
A
pretext cleanupfunction could get the hash of every cached image and save only those that are still in the document.Related to #1218, but not automatic. The cleanup command should also prune the logs (maybe completely), depending on what the automatic policy is.