qvm-copy restore to 4.1 functionality with "allow-symlinks" option

[humanrights0218]

How to file a helpful issue

The problem you're addressing (if any)

The qvm copy functionality makes several breaking changes since 4.1 One such change was fixed in 4.2.2 with the +allow-all-names.

Currently, copying symlinks is still impossible. I think should be allowed with an 'allow-symlinks' options.

The current work around of using tar does not work in all use cases. For example, it could literally be impossible depending on free disk space let alone the amount of time it could take on large datasets.

The solution you'd like

"allow-symlinks" to enable the copying of symlinks between VMs

The value to a user, and who that user might be

Restore functionality back to 4.1. Makes copying possible where it is impossible now.

[andrewdavidwong]

Related issues: #8581, #8332

Based on the discussion on #8581, it sounds like the devs have decided against doing this. However, I'll wait for confirmation that that's still the case before closing.

[jamke]

I would vote for it.
I would love to have a reliable way of copying files as is, especially considering it would be opt-in option.
P.S. Has copying as is in Qubes OS R1.0-R4.0 ever caused any issues for anybody really?