tar: Support winsymlinks:nativestrict winsymlinks:native properly when the target file is in the tar archive.

[lygstate]

Currently, even though the symbolic link target exist in the tar arhive, sill would fail, because the target are extracted latter before the symbloic link,
we can add code to handle this special case, maybe needs upstream to tar.

[lazka]

With msys2/msys2-runtime#114 we could force package build envs to support symlinks.We still have to make sure they don't end up in packages though.

[lygstate]

With msys2/msys2-runtime#114 we could force package build envs to support symlinks.We still have to make sure they don't end up in packages though.

That's a copy, a different topic,

[lazka]

Last time I looked at the tar code it was not obvious how to re-order things, it extracts them in the order it reads them from the archive. That's why I'm suggesting an alternative (long term) fix.

[lygstate]

Last time I looked at the tar code it was not obvious how to re-order things, it extracts them in the order it reads them from the archive. That's why I'm suggesting an alternative (long term) fix.

Thanks, I have an idea, that tar first creating the directory tree, then override it, only when the OS support that.

[lygstate]

Last time I looked at the tar code it was not obvious how to re-order things, it extracts them in the order it reads them from the archive. That's why I'm suggesting an alternative (long term) fix.

Oh, a new idea, the tar can save the list of symbloic links that can not created natively with windows api, then after all files ar extracted,
walking that list of saved symbloic links can not directly created, try re-create them, the issue will be resolved.