Stuart Henderson <[email protected]> writes: > Agreed on all points. The "not reachable" for libinotify is a limitation of > check-lib-depends which doesn't handle libraries in > directories other than /usr/local/lib correctly.
thanks for the clarification :)
> The other question is whether there's any point keeping sxiv separately. I
> think I would add a sxiv->nsxiv symlink and replace it
> (quirks, @pkgpath, @conflict)
something like this? (plus the removal of graphics/sxiv ofc)
@comment $OpenBSD: PLIST,v$
@conflict sxiv-*
@pkgpath graphics/sxiv
@bin bin/nsxiv
bin/sxiv
...
Index: Makefile
===================================================================
RCS file: /home/cvs/ports/devel/quirks/Makefile,v
retrieving revision 1.1344
diff -u -p -r1.1344 Makefile
--- Makefile 23 Jan 2022 17:10:07 -0000 1.1344
+++ Makefile 3 Feb 2022 10:51:04 -0000
@@ -5,7 +5,7 @@ CATEGORIES = devel databases
DISTFILES =
# API.rev
-PKGNAME = quirks-4.97
+PKGNAME = quirks-4.98
PKG_ARCH = *
MAINTAINER = Marc Espie <[email protected]>
Index: files/Quirks.pm
===================================================================
RCS file: /home/cvs/ports/devel/quirks/files/Quirks.pm,v
retrieving revision 1.1361
diff -u -p -r1.1361 Quirks.pm
--- files/Quirks.pm 23 Jan 2022 17:10:07 -0000 1.1361
+++ files/Quirks.pm 3 Feb 2022 10:48:32 -0000
@@ -695,6 +695,7 @@ my $stem_extensions = {
'apertium-mk-en' => 'apertium-mkd-eng',
'apertium-pt-ca' => 'apertium-por-cat',
'pinentry-gtk2' => 'pinentry-gnome3',
+ 'sxiv' => 'nsxiv',
};
my $obsolete_reason = {};
nsxiv.tar.gz
Description: Binary data
