changelog

[makedoc]

CHANGES/v2.2.txt

@@ -84,5 +84,9 @@ download PLUMED from github.
 
 For users:
 - Module activation can now be controlled during configure with `--enable-modules` option.
+- Almost complete refactoring of installation procedure. Now
+  DESTDIR and other standard autoconf directories (e.g. bindir) are completely supported.
+  Additionally, everything should work properly also when directory names include spaces (\issue{157}).
+  Finally, compiler is not invoked on install unless path are explicitly changed (\issue{107}).
 
 */

user-doc/Installation.txt

@@ -319,14 +319,20 @@ If you didn't specify the `--prefix` option during configure, and you did not se
 variable when installing, PLUMED will be installed in /usr/local.
 The install command should be executed with root permissions (e.g. "sudo make install")
 if you want to install PLUMED on a system directory.
-Notice that upon installation PLUMED currently needs to relink a library. If
-root user does not have access to compilers, "sudo -E make install" might solve
+
+Notice that upon installation PLUMED might need to relink a library.
+This was always true until version 2.1, but in version 2.2 libraries should
+only be relinked if one changes the install prefix during when typing `make install`.
+If root user does not have access to compilers, "sudo -E make install" might solve
 the issue.
-An almost full copy of the compilation directory will
-be installed into $prefix/lib/plumed/ directory. A link to the proper
-PLUMED executable will be set up in $prefix/bin,
-PLUMED include files will be copied to $prefix/include/plumed
-and PLUMED libraries will be linked to $prefix/lib.
+
+Upon install, executables are copied to $prefix/bin, libraries to $prefix/lib,
+include files to $prefix/include, and
+documentation to $prefix/shared/doc/plumed. Additionally, a directory
+$prefix/lib/plumed is created containing several other files, including
+patch files, object files (for static patches), etc.
+Notice also that these path can be further customized using standard autoconf
+directories (e.g. `./configure --bindir=/usr/bin64`).
 
 One should then set the environment properly. We suggest to do it using
 the module framework (http://modules.sourceforge.net). An ad hoc generated