- Fix an issue where netcams were not connecting [1]

- When motion was updated to 4.x, it was overlooked that the default
  search path for the configuration files was changed. This was causing
  existing configurations to not be read. Fix the port to install
  default configuration in correct location and add an UPDATING message
  giving users the proper instructions on where to place their existing
  conf files. [2]
- Create an empty ${ETCDIR}/conf.d directory that can optionally be used
  to dump camera configs in instead of creating separate lines for each
  one in motion.conf
- Add some missing PORTDOCS and install with the correct mode
- Make the VIDEO options OPTIONS_RADIO instead of OPTIONS_SINGLE to
  allow for netcam only support (suggested in [2])
- Fix bad logic in configure.ac that was causing V4L to not be dectected
  when the PWCBSD option was enabled

PR:		216189 [1]
Reported by:	Charles P <charlespigott@googlemail.com>
Patched by:	<anthony@ury.org.uk>
Obtained from:	upstream
PR:		216466 [2]
Reported by:	<bakhur@inbox.ru>, tdb@
Pointy hat to:	jhale
MFH:		2017Q1 (blanket)

1 files changed, 25 insertions, 0 deletions

diff --git a/UPDATING b/UPDATING
index d93b5cbe9e06..e976fce87727 100644
--- a/UPDATING
+++ b/UPDATING
@@ -5,6 +5,31 @@ they are unavoidable.
 You should get into the habit of checking this file for changes each time
 you update your ports collection, before attempting any port upgrades.
 
+20170129:
+  AFFECTS: users of multimedia/motion
+  AUTHOR: jhale@FreeBSD.org
+
+  Version 3.x expected the configuration files to reside in:
+	${LOCALBASE}/etc
+  Version 4.x expects the configuration files to reside in:
+	${LOCALBASE}/etc/motion
+  This was unfortunately overlooked when the port was updated to 4.x, but it
+  has now been fixed to install the default configuration file in the new
+  location. The rc script now checks for motion.conf in the new location.
+
+  While you may be able to simply copy your old motion.conf to the new location,
+  it is recommended to review ${LOCALBASE}/etc/motion/motion.conf and make
+  changes to it based on your old ${LOCALBASE}/etc/motion.conf as some options
+  have been added and removed.
+
+  Further, if you use motion with multiple cameras and have
+  ${LOCALBASE}/etc/thread[0-9].conf files, they should be moved to
+  ${LOCALBASE}/etc/motion as well. These files are deprecated and should be
+  renamed to camera[0-9].conf and in motion.conf, lines like:
+	thread /usr/local/etc/thread1.conf
+  Should be converted to:
+	camera /usr/local/etc/motion/camera1.conf
+
 20170127:
   AFFECTS: users of www/uwsgi
   AUTHOR: feld@FreeBSD.org