Version
6.4.3 (commit 70f8e6a1d, devel branch)
Description
While testing with the newest devel branch, some of my use cases broke due to a change in behavior of ly_ctx_set_searchdir().
The documentation states that the current working directory is searched automatically but not recursively, while explicitly registered search directories are searched recursively. In practice, the current working directory's subdirectories now get recursively searched too, as soon as any explicit search directory is also registered.
The practical consequence is that a module lookup with no revision specified can pick up an unrelated, same-named module file located anywhere under the current working directory, instead of the one in the directory that was actually registered as a search path.
Is this an intended change, or a regression? For now I can mitigate this with the LY_CTX_DISABLE_SEARCHDIR_CWD flag.
Version
6.4.3 (commit
70f8e6a1d,develbranch)Description
While testing with the newest devel branch, some of my use cases broke due to a change in behavior of
ly_ctx_set_searchdir().The documentation states that the current working directory is searched automatically but not recursively, while explicitly registered search directories are searched recursively. In practice, the current working directory's subdirectories now get recursively searched too, as soon as any explicit search directory is also registered.
The practical consequence is that a module lookup with no revision specified can pick up an unrelated, same-named module file located anywhere under the current working directory, instead of the one in the directory that was actually registered as a search path.
Is this an intended change, or a regression? For now I can mitigate this with the
LY_CTX_DISABLE_SEARCHDIR_CWDflag.