When working with pants to build standalone pex files.
Is there an opinionated way to change the dist path in the relevant BUILD filed?
It seems the output path option only changes the name of the object being generated not the dist path itself.
My use case is keeping modules in version control via lfs, where each pex file represents a snapshot of a given release.
To this end, does pants keep track of the build/package state of pex files?
i.e. when triggering