Document MONO_PATH behaviour for relative paths

Tha previous behaviour of MONO_PATH for relative paths (that implied
using the paths as relative to the current directory when loading
assemblies) was not yet documented and led to some failures when
executing tests.

In order to fix the failures, a new behaviour has been introduced:
relative paths are resolved at launch time, so that the folders which
are examined when loading assemblies do not depend on the current path
of the program.

This patchset is released under the MIT license.

diff --git a/man/mono.1 b/man/mono.1
index 99be6c4f23b068b06e9863d6c93a24fdf7aebbb3..45659dafead517dfa9be41bd3d17b7c542fac6bf 100644 (file)
--- a/man/mono.1
+++ b/man/mono.1
@@ -1356,6 +1356,8 @@ loader in subtle ways.
 Directories are separated by the platform path separator (colons on unix). Example:
 .B /home/username/lib:/usr/local/mono/lib
 .Sp
+Relative paths are resolved based on the launch-time current directory.
+.Sp
 Alternative solutions to MONO_PATH include: installing libraries into
 the Global Assembly Cache (see gacutil(1)) or having the dependent
 libraries side-by-side with the main executable.