Commits on Jun 6, 2024

1. Fix relative symlinks copying …

   All relative paths of symbolic links should be resolved from the
   directory where the link is located. The current working directory
   does not affect the resolution of the path. A symbolic link can
   be absolute or relative, and may or may not have a leading dot.
   Directory content example:
   file
   symlink -> file
   Copying of the directory with such content does not work currently.
   When copying `symlink`, `Copy` returns an error because the `file`
   does not exist in the current working directory. In the existing
   tests, there is a symbolic link named "symlink" that points to a
   file named "README.md". However, when resolving the path of the
   file, the file is located in the repository's root directory,
   not the test case directory, and copying of these dirs work fine.
   
   The solution is to check whether the resolved path is absolute
   or not. If it is not, append it to the file's directory path.

   

   psergee committed Jun 6, 2024
   Configuration menu

   • View commit details
   • Copy full SHA for 1ddce65
   • Browse repository at this point

   Copy the full SHA

   1ddce65 View commit details

   Browse the repository at this point in the history