fuse-ntfs-3g

[Greg Troxel <gdt%lexort.com@localhost>]

Trying to build fuse-ntfs-3g, I find an unhelpful "ancient API" comment
in a NOT_FOR line, not specifying which version is needed and which is
present.

Removing that and building, I see errors, but the real issue is unclear
without investigating more.

Using filesystems/fuse instead, the package builds.  This is a good
argument for a package-settable variable about acceptable fuse
libraries.

I think, but am not quite sure, that the real issue here is that
fuse-ntfs-3g uses the low-level fuse API, or at least I find that in the
sources.  It may just be API version issues.

So, any reason not to adjust?  Anybody who is willing to admit to having
an NTFS filesystem want to test?  I'll commit in 24h absent objections
with rationale.

--- Makefile.~1.20~	2019-04-15 16:08:40.219806761 -0400
+++ Makefile	2019-04-15 16:10:15.931530825 -0400
@@ -10,12 +10,21 @@ COMMENT=	NTFS driver with read and write
 CONFIGURE_ARGS+=	--disable-ntfsprogs
 CONFIGURE_ARGS+=	--enable-mount-helper
 
-NOT_FOR_PLATFORM=	NetBSD-*-* # ancient fuse API
-
 BUILD_DIRS=	src
 
 USE_TOOLS+=	pkg-config
 
+.include "../../mk/bsd.prefs.mk"
+
 .include "../../filesystems/libntfs/buildlink3.mk"
+.if ${OPSYS} == "NetBSD"
+.include "../../filesystems/perfuse/buildlink3.mk"
+# fuse-ntfs-3g does not build with librefuse from netbsd-8.
+# \todo Add a mechanism in mk/fuse.buildlink3.mk to declare this, rather
+# than open-coding the changing of which bl3 line is used.
+.include "../../filesystems/fuse/buildlink3.mk"
+.else
+# Find this platform's preferred FUSE implementation (normal approach). 
 .include "../../mk/fuse.buildlink3.mk"
+.endif
 .include "../../mk/bsd.pkg.mk"