[Midnightbsd-cvs] mports [22516] trunk/devel/libinotify: update inotify

[laffer1 at midnightbsd.org]

Revision: 22516
          http://svnweb.midnightbsd.org/mports/?rev=22516
Author:   laffer1
Date:     2017-09-23 18:11:03 -0400 (Sat, 23 Sep 2017)
Log Message:
-----------
update inotify

Modified Paths:
--------------
    trunk/devel/libinotify/Makefile
    trunk/devel/libinotify/distinfo
    trunk/devel/libinotify/pkg-descr
    trunk/devel/libinotify/pkg-message
    trunk/devel/libinotify/pkg-plist

Removed Paths:
-------------
    trunk/devel/libinotify/files/

Modified: trunk/devel/libinotify/Makefile
===================================================================
--- trunk/devel/libinotify/Makefile	2017-09-23 22:08:00 UTC (rev 22515)
+++ trunk/devel/libinotify/Makefile	2017-09-23 22:11:03 UTC (rev 22516)
@@ -1,7 +1,7 @@
 # $MidnightBSD$
 
 PORTNAME=	libinotify
-PORTVERSION=	20150516
+PORTVERSION=	20160505
 CATEGORIES=	devel
 
 MAINTAINER=	ports at MidnightBSD.org
@@ -12,20 +12,15 @@
 FAKE_OPTS=	trueprefix
 
 USE_GITHUB=	yes
-GH_ACCOUNT=	dmatveev
+GH_ACCOUNT=	libinotify-kqueue
 GH_PROJECT=	libinotify-kqueue
-GH_COMMIT=	f4a092a
-GH_TAGNAME=	${GH_COMMIT}
+GH_TAGNAME=	417e789
 
-WRKSRC=		${WRKDIR}/libinotify-kqueue-${GH_COMMIT}
+WRKSRC=		${WRKDIR}/libinotify-kqueue-${GH_TAGNAME}
 
+USES=		autoreconf libtool
+GNU_CONFIGURE=	yes
 USE_LDCONFIG=	yes
+INSTALL_TARGET=	install-strip
 
-post-patch:
-	@${CP} ${FILESDIR}/Makefile ${WRKSRC}
-	@${TOUCH} ${WRKSRC}/config.h
-	@echo "#define HAVE_PTHREAD_BARRIER 1" >> ${WRKSRC}/config.h
-	@echo "#define BUILD_LIBRARY 1" >> ${WRKSRC}/config.h
-	@echo "#include <sys/tree.h>" >> ${WRKSRC}/config.h
-
 .include <bsd.port.mk>

Modified: trunk/devel/libinotify/distinfo
===================================================================
--- trunk/devel/libinotify/distinfo	2017-09-23 22:08:00 UTC (rev 22515)
+++ trunk/devel/libinotify/distinfo	2017-09-23 22:11:03 UTC (rev 22516)
@@ -1,2 +1,3 @@
-SHA256 (libinotify-20150516_GH0.tar.gz) = ad001b8229e83d379d41c0add348cff97b50c07ce60cf3f78aff86ddd18bdda3
-SIZE (libinotify-20150516_GH0.tar.gz) = 42543
+TIMESTAMP = 1506204542
+SHA256 (libinotify-20160505_GH0.tar.gz) = 706b8e257a7adf986f928fb3bc8de37e763b6692b6a6875396be64c3e82447ae
+SIZE (libinotify-20160505_GH0.tar.gz) = 67298

Modified: trunk/devel/libinotify/pkg-descr
===================================================================
--- trunk/devel/libinotify/pkg-descr	2017-09-23 22:08:00 UTC (rev 22515)
+++ trunk/devel/libinotify/pkg-descr	2017-09-23 22:11:03 UTC (rev 22516)
@@ -5,4 +5,4 @@
 The IN_OPEN, IN_CLOSE_WRITE and IN_CLOSE_NOWRITE events are not yet
 implemented, so the relevant tests are known to fail.
 
-WWW: https://github.com/dmatveev/libinotify-kqueue
+WWW: https://github.com/libinotify-kqueue/libinotify-kqueue

Modified: trunk/devel/libinotify/pkg-message
===================================================================
--- trunk/devel/libinotify/pkg-message	2017-09-23 22:08:00 UTC (rev 22515)
+++ trunk/devel/libinotify/pkg-message	2017-09-23 22:11:03 UTC (rev 22516)
@@ -1,8 +1,44 @@
+============================================================================
+
+Libinotify functionality on BSD is missing support for
+
+  - detecting a file being moved into or out of a directory within the
+    same filesystem
+  - certain modifications to a symbolic link (rather than the
+    file it points to.)
+
+in addition to the known limitations on all platforms using kqueue(2)
+where various open and close notifications are unimplemented.
+
+This means the following regression tests will fail:
+
+Directory notifications:
+   IN_MOVED_FROM
+   IN_MOVED_TO
+
+Open/close notifications:
+   IN_OPEN
+   IN_CLOSE_NOWRITE
+   IN_CLOSE_WRITE
+
+Symbolic Link notifications:
+   IN_DONT_FOLLOW
+   IN_ATTRIB
+   IN_MOVE_SELF
+   IN_DELETE_SELF
+
+Kernel patches to address the missing directory and symbolic link
+notifications are available from:
+
+https://github.com/libinotify-kqueue/libinotify-kqueue/tree/master/patches
+
+=============================================================================
 You might want to consider increasing the kern.maxfiles tunable if you plan
 to use this library for applications that need to monitor activity of a lot
 of files.
 
-For a typical desktop, add the following line to /boot/loader.conf, then
-reboot the system:
+If the default on your system is too low, add the following line to
+/boot/loader.conf, then reboot the system:
 
     kern.maxfiles="25000"
+=============================================================================

Modified: trunk/devel/libinotify/pkg-plist
===================================================================
--- trunk/devel/libinotify/pkg-plist	2017-09-23 22:08:00 UTC (rev 22515)
+++ trunk/devel/libinotify/pkg-plist	2017-09-23 22:11:03 UTC (rev 22516)
@@ -1,3 +1,5 @@
 include/sys/inotify.h
+lib/libinotify.a
 lib/libinotify.so
 lib/libinotify.so.0
+lib/libinotify.so.0.0.0