[vcpkg] implement copy_symlink working for non-elevated processes#12400
[vcpkg] implement copy_symlink working for non-elevated processes#12400ras0219-msft merged 14 commits intomicrosoft:masterfrom
Conversation
| { | ||
| #if defined(_WIN32) | ||
| const DWORD flags = SYMBOLIC_LINK_FLAG_ALLOW_UNPRIVILEGED_CREATE; | ||
| if (!CreateSymbolicLinkW(newpath.c_str(), oldpath.c_str(), flags)) |
There was a problem hiding this comment.
This doesn't work, I don't think -- this has newpath be a symlink for oldpath, which requires that oldpath continues existing; what you really want is newpath to be a symlink to the thing oldpath points to. Maybe you want:
| if (!CreateSymbolicLinkW(newpath.c_str(), oldpath.c_str(), flags)) | |
| if (!CreateSymbolicLinkW(newpath.c_str(), fs::stdfs::read_symlink(oldpath).c_str(), flags)) |
There was a problem hiding this comment.
Is that okay, that symlink points to packages folder?
In either case fs::stdfs::read_symlink does not work at all: _Map_mode from filesys.cpp does not check FILE_ATTRIBUTE_REPARSE_POINT and does not return file_type::symlink.
Furthermore _Symlink_get returns empty string. It's not implemented yet in my VS 2019.
There was a problem hiding this comment.
It's not okay; this is not a copy_symlink at all, it's a create_symlink
There was a problem hiding this comment.
Than read_symlink is not a solution, even if it works. Right?
The proper logic will be:
- get target of oldpath (it's in packages)
- map oldpath to new_oldpath (the original file copied from packages to installed folder)
- create symlink newpath targeted to new_oldpath
Right?
There was a problem hiding this comment.
It's not okay; this is not a copy_symlink at all, it's a create_symlink
Or what did you mean? What should happen, when vcpkg copies file_v1 + file (symlink pointed to file_v1) from packages to installed folder?
There was a problem hiding this comment.
That's not a question I'm interested in answering -- we want copy_symlink to do what copy_symlink says it does. That means, take a file that is a symlink, and copy that file (i.e., create a new file with the same target as the original symlink). copy_symlink needs to do that, not create a new symlink that links to the old file.
There was a problem hiding this comment.
std::experimental::filesystem will never be updated to support symlinks; it will be left in a bug for bug compatible with VS2015 state. That implementation had too many bugs and the filesystem TS vs. what got standardized were too divergent to share implementations. std::filesystem is a complete replacement implementation that does support symlinks. As a result _Map_mode will never be changed to enable such support.
The only symlinks that make sense here are relative symlinks, that when copied, still form the correct path in their new location. The "packages" directory is not generally persistent; for example when packages are restored from a binary cache only the 'installed' directory is restored. As a result I don't believe this change will ever persist a symlink correctly :(
|
Why can't we use |
and |
Co-authored-by: nicole mazzuca <mazzucan@outlook.com>
Co-authored-by: nicole mazzuca <mazzucan@outlook.com>
Co-authored-by: nicole mazzuca <mazzucan@outlook.com>
There was a problem hiding this comment.
Just some more minor changes, then I'm good with merging :)
It's still not perfect; given a -> b -> c (a, b symlinks with a pointing to b, b pointing to c), copy_symlink(a, d) will give you d -> c, whereas in a perfect world you'd get d -> b -> c. Unfortunately, Windows does not support this feature without using DeviceIoControl, and so I'm willing to deal with this for now. When we rewrite the files code to remove std::filesystem, that'll be a thing to do -- specifically, using https://docs.microsoft.com/en-us/windows-hardware/drivers/ifs/fsctl-get-reparse-point
Co-authored-by: nicole mazzuca <mazzucan@outlook.com>
Co-authored-by: nicole mazzuca <mazzucan@outlook.com>
Co-authored-by: nicole mazzuca <mazzucan@outlook.com>
Co-authored-by: nicole mazzuca <mazzucan@outlook.com>
Co-authored-by: nicole mazzuca <mazzucan@outlook.com>
|
Thanks everyone! |
|
Unfortunately this implements |
|
I've asked about symlinks pointed to packages folder. |
|
@Maximus5 I see; sorry for not noticing before; I just found this PR through a 'git blame'. |
…crosoft#12400) * [vcpkg] implement copy_symlink working for non-elevated processes * [vcpkg] read_symlink Windows implementation * [vcpkg] normalize_path on Windows only * Update toolsrc/src/vcpkg/base/files.cpp Co-authored-by: nicole mazzuca <mazzucan@outlook.com> * Update toolsrc/src/vcpkg/base/files.cpp Co-authored-by: nicole mazzuca <mazzucan@outlook.com> * Update toolsrc/src/vcpkg/base/files.cpp Co-authored-by: nicole mazzuca <mazzucan@outlook.com> * remove normalization * Update toolsrc/src/vcpkg/base/files.cpp Co-authored-by: nicole mazzuca <mazzucan@outlook.com> * Update toolsrc/src/vcpkg/base/files.cpp Co-authored-by: nicole mazzuca <mazzucan@outlook.com> * Update toolsrc/src/vcpkg/base/files.cpp Co-authored-by: nicole mazzuca <mazzucan@outlook.com> * Update toolsrc/src/vcpkg/base/files.cpp Co-authored-by: nicole mazzuca <mazzucan@outlook.com> * Update toolsrc/src/vcpkg/base/files.cpp Co-authored-by: nicole mazzuca <mazzucan@outlook.com> * use unique_ptr * comments Co-authored-by: nicole mazzuca <mazzucan@outlook.com>
Function
fs::stdfs::copy_symlinkused byinstall_files_and_write_listfilerequires the vcpkg process to be running elevated (Windows). Otherwise it always failed withoperation not permittederror.This PR fixes inability to copy symlink in non-elevated processes.
I tried to instal libressl via command
Description of the problem is here: #11949 (comment)