Right now when packaging a relative symlink that points somewhere outside of the package root CIPD complains "Error: Invalid symlink <path>: a relative symlink pointing to a file outside of the package root."

Maybe we should transparently just put the symlink target into the package in this case?

This happens when repackaging files already deployed by CIPD (using 'symlink' method), perhaps into a .cipd dir that are multiple level above, e.g.

$ cipd create --pkg-def cipd.yaml -tag version:4.0-cr0
...
Error: Invalid symlink lib/android-all-4.3_r2-robolectric-0.jar: a relative symlink pointing to a file outside of the package root.

$ ls clankium/src/third_party/robolectric/lib/ I get
...
android-all-4.3_r2-robolectric-0.jar -> ../../../../.cipd/pkgs/49/_current/lib/android-all-4.3_r2-robolectric-0.jar
...