Update upstream source from tag 'upstream/1.0.32'

Update to upstream version '1.0.32'
with Debian dir 2c1111c59d9d68bcbf479a4a4de7697fe2de127f

1 files changed, 17 insertions, 4 deletions

diff --git a/README b/README
index 3614b8d..be4699f 100644
--- a/README
+++ b/README
@@ -29,6 +29,17 @@ make install
 
 man sane
 
+Pre-built binaries:
+===================
+
+In addition to versions included in releases, some platforms have more current versions available.
+
+Ubuntu PPA https://launchpad.net/~sane-project/+archive/ubuntu/sane-release
+
+sudo add-apt-repository ppa:sane-project/sane-release
+sudo apt update
+apt install libsane libsane-common sane-utils
+
 
 Prerequisites
 =============
@@ -134,10 +145,12 @@ configure options, there are the following SANE specific options:
 	Means, that some backends will use a lockfile for allowing multiple
 	access to one scanner. This is useful, i.e. one frontend is scanning
 	the button status and another one will scan. The path to the lock
-	files is define by --localstatedir at the configure step and is
-	$localstatedir/lock/sane. The default group is uucp and can be
-	changed by using --with-group=newgroup. If you do not want any
-	backend to use a lockfile, simply use --disable-locking.
+	files is defined by --localstatedir at the configure step and is
+	$localstatedir/lock. The default group is uucp and can be changed
+	by using --with-group=newgroup. If you do not want any backend to
+	use a lockfile, simply use --disable-locking.
+	Note: The Plustek backend is currently the only backend that makes
+	      use of this feature.
 
 To limit the backends that are compiled, set the variable BACKENDS to
 the list of backends to compile.  The following will limit compiling