clean_fakechroot.py is an artifact of our debian container build process's messiness; there may be a way to avoid needing this special clean-up, and if so, we should take advantage of it.
One possibility: could we run our tar executable inside of fakechroot, so that the links are resolved correctly?
This is not very high-priority, but would be a nice simplification.
clean_fakechroot.py
is an artifact of our debian container build process's messiness; there may be a way to avoid needing this special clean-up, and if so, we should take advantage of it.One possibility: could we run our tar executable inside of fakechroot, so that the links are resolved correctly?
This is not very high-priority, but would be a nice simplification.