Merge branch 'future-doc'

Author: doublep

doc/README.adoc

@@ -48,6 +48,7 @@
 :uri-docker-emacs: https://github.com/Silex/docker-emacs
 :uri-release-it: https://github.com/release-it/release-it
 :uri-emacs-forwarding: https://debbugs.gnu.org/cgi/bugreport.cgi?bug=56745
+:uri-guix: https://guix.gnu.org/
 :since-0-1-1: image:https://img.shields.io/badge/since-0.1.1-8be[Since 0.1.1,float=right]
 :since-0-2: image:https://img.shields.io/badge/since-0.2-8be[Since 0.2,float=right]
 :since-0-2-1: image:https://img.shields.io/badge/since-0.2.1-8be[Since 0.2.1,float=right]
@@ -70,6 +71,7 @@
 :since-1-6: image:https://img.shields.io/badge/since-1.6-8be[Since 1.6,float=right]
 :since-1-7: image:https://img.shields.io/badge/since-1.7-8be[Since 1.7,float=right]
 :since-1-8: image:https://img.shields.io/badge/since-1.8-8be[Since 1.8,float=right]
+:since-1-9: image:https://img.shields.io/badge/since-1.9-8be[Since 1.9,float=right]
 
 
 toc::[]

doc/project-dependencies.adoc

@@ -297,6 +297,42 @@ Current list of the known tools:
 * `elisp-lint`
 * `undercover`
 
+[#disabling-dependencies]
+=== Disabling dependency management
+
+CAUTION: This operation mode is *not recommended*.  It exists only to
+support special usecases that “insist” on setting Emacs’ `load-path`
+directly and cannot be customized (with reasonable effort).
+
+{since-1-9} Eldev has limited support for operating _without
+dependency management_.  This mode can be activated using global
+option `--disable-dependencies` (there is no short version to
+emphasize that _it is not recommended_).  It exists to support certain
+environments that themselves provide a suitable value for Emacs
+variable `load-path` via environment variable `EMACSLOADPATH`.  An
+example of such an environment is {uri-guix}[GUIX] package building.
+
+Unlike in <<preinstalled-dependencies,preinstalled-dependency mode>>
+described earlier, here Eldev doesn’t work with dependencies (and
+<<development-tool-sources,tools>>) as standard Emacs packages at all.
+Instead, everything is expected to be loadable using `require` form
+without any further setup.  For this, variable `load-path` must be set
+appropriately, most likely using `EMACSLOADPATH` (though you could, in
+principle, set its value in e.g. `Eldev-local`).
+
+One consequence of this mode is that Emacs package system won’t
+consider dependency packages installed at all, see
+`package-installed-p`.  <<autoloads,Autoloads>> are not supported in
+this mode (neither for dependencies nor for the project itself), so
+you must explicitly require all features before using them.  There
+might be other, unexpected, limitations as well, as this mode is not
+thoroughly tested.
+
+Unless you need to build packages for GUIX or have some comparable
+environment that computes `load-path` on its own and doesn’t let Eldev
+manage dependencies normally by accessing standard package archives,
+you shouldn’t use this mode.
+
 [#global-cache]
 === Global package archive cache
 

doc/setup-procedure.adoc

@@ -71,6 +71,7 @@ from affecting your Emacs and, finally, to simplify testing of certain
 * Eldev supports <<different-emacs-versions,executing on different
   Emacs version>> for the same project without any additional steps.
 
+[#preinstalled-dependencies]
 === Using preinstalled dependencies
 
 {since-0-8} Starting with version 0.8 you can opt out of some of the
@@ -102,3 +103,7 @@ to test on <<different-emacs-versions,different Emacs versions>> in
 external directory mode.  Therefore, it is not the default.  But, as
 usual in Eldev, you can make it the default in file
 `~/.config/eldev/config` if you want.
+
+There is also a way to <<disabling-dependencies,disable dependency
+management>> _completely_.  However, other than in few very special
+cases you should prefer normal operation.