What do you think about the idea of deleting keepassx and set a pkgpath
in keepassxc?

Here is a quote from the keepassxc FAQ:

Q: Why KeePassXC instead of KeePassX?
A: KeePassX is an amazing password manager, but hasn't seen much active
development for quite a while. Many good pull requests were never merged
and the original project is missing some features which users can expect
from a modern password manager. Hence, we decided to fork KeePassX to
continue its development and provide you with everything you love about
KeePassX plus many new features and bugfixes.

-- https://keepassxc.org/docs/#faq-keepassx


Everything keepassx can do, so can keepassxc and more. "File format
compatibility with KeePass2, KeePassX, MacPass, KeeWeb and many others
(KDBX 3.1 and 4.0)"

It feels so right!

RS


Index: Makefile
===================================================================
RCS file: /cvs/ports/security/keepassxc/Makefile,v
retrieving revision 1.27
diff -u -p -u -p -r1.27 Makefile
--- Makefile    20 Jan 2020 06:28:12 -0000      1.27
+++ Makefile    22 Feb 2020 06:33:57 -0000
@@ -4,6 +4,7 @@ COMMENT =       management tool for password a
 
 V =            2.5.3
 DISTNAME =     keepassxc-${V}
+REVISION =     0
 
 CATEGORIES =   security
 
Index: pkg/PLIST
===================================================================
RCS file: /cvs/ports/security/keepassxc/pkg/PLIST,v
retrieving revision 1.18
diff -u -p -u -p -r1.18 PLIST
--- pkg/PLIST   20 Jan 2020 06:28:12 -0000      1.18
+++ pkg/PLIST   22 Feb 2020 06:33:57 -0000
@@ -1,4 +1,5 @@
 @comment $OpenBSD: PLIST,v 1.18 2020/01/20 06:28:12 rsadowski Exp $
+@pkgpath security/keepassx
 @bin bin/keepassxc
 @bin bin/keepassxc-cli
 %%browser%%

Reply via email to