Description
In general, the paths for Teleport work exactly as needed. There are certain circumstances, through no fault of Teleport, that can cause complication, however. One such circumstance is when the workspace directory is among the paths being included in the tpl. In this case, it can cause an infinite chain of links/directories. While this is a special circumstance, now that Teleport can be used for Extras, it raises the question of whether alternate workspace and output directories should be considered.
Of course, --push --target=path/to/dir/ is an option, but this only resolves upon completion, and does not affect the workspace directory. Further, the workspace only gets cleaned after the package has been written. While the average circumstance requires no such option, adding the option will allow immediate circumvention of issues similar to the one above. Additionally, it would add value to other tools that might depend upon Teleport as a library/class resource rather than simply a CLI tool.