Re: [UPDATE]: security/kc - enable YubiKey support, add -yubikey flavor
On 2024/04/01 12:47, Lévai, Dániel wrote: > Ping? > > Original Message > On 27/03/2024 16:33, Lévai, Dániel wrote: > > > > Hi all, > > > > > > This is a patch to enable YubiKey support with a new -yubikey flavor. > > > I invite anyone to test it; it works for me(tm), but requires some > > fiddling with the USB device files - hence the package message. > > > > > > Any ideas, suggestions are welcome, > > > Daniel > > > > Barring any objections, issues, what do you think about committing? > > > > Daniel Committed with a few tweaks.
Re: [UPDATE]: security/kc - enable YubiKey support, add -yubikey flavor
Ping? Original Message On 27/03/2024 16:33, Lévai, Dániel wrote: > > Hi all, > > > > This is a patch to enable YubiKey support with a new -yubikey flavor. > > I invite anyone to test it; it works for me(tm), but requires some > fiddling with the USB device files - hence the package message. > > > > Any ideas, suggestions are welcome, > > Daniel > > Barring any objections, issues, what do you think about committing? > > Daniel signature.asc Description: OpenPGP digital signature
Re: [UPDATE]: security/kc - enable YubiKey support, add -yubikey flavor
> Hi all,
>
> This is a patch to enable YubiKey support with a new -yubikey flavor.
> I invite anyone to test it; it works for me(tm), but requires some fiddling
> with the USB device files - hence the package message.
>
> Any ideas, suggestions are welcome,
> Daniel
Barring any objections, issues, what do you think about committing?
Danieldiff --git a/security/kc/Makefile b/security/kc/Makefile
index ac9e76e7e60..f1fdbbd2676 100644
--- a/security/kc/Makefile
+++ b/security/kc/Makefile
@@ -11,6 +11,9 @@ MAINTAINER = LEVAI Daniel
# BSD
PERMIT_PACKAGE = Yes
+FLAVORS= yubikey
+FLAVOR?=
+
WANTLIB += c crypto curses edit scrypt util xml2
LIB_DEPENDS = textproc/libxml \
@@ -18,6 +21,15 @@ LIB_DEPENDS = textproc/libxml \
MAKE_ENV += OS_OPENBSD=yes HAVE_LIBSCRYPT=yes
+.if ${FLAVOR:Myubikey}
+WANTLIB += ykpers-1 yubikey
+
+LIB_DEPENDS += security/yubico/yubikey-personalization \
+ security/yubico/yubico-c
+
+MAKE_ENV += HAVE_YUBIKEY=yes
+.endif
+
post-install:
${INSTALL_DATA_DIR} ${PREFIX}/share/doc/kc
${INSTALL} ${WRKBUILD}/Changelog.md ${PREFIX}/share/doc/kc/
diff --git a/security/kc/pkg/MESSAGE b/security/kc/pkg/MESSAGE
index 345fc451266..303ac67cddb 100644
--- a/security/kc/pkg/MESSAGE
+++ b/security/kc/pkg/MESSAGE
@@ -1 +1,3 @@
Please read ${PREFIX}/share/doc/kc/Changelog.md to see why you might not be able to open your database anymore.
+
+Using YubiKey support with the -yubikey flavor requires read/write access to the /dev/usb? and /dev/ugen?.?? devices.
[UPDATE]: security/kc - enable YubiKey support, add -yubikey flavor
Hi all,
This is a patch to enable YubiKey support with a new -yubikey flavor.
I invite anyone to test it; it works for me(tm), but requires some fiddling
with the USB device files - hence the package message.
Any ideas, suggestions are welcome,
Danieldiff --git a/security/kc/Makefile b/security/kc/Makefile
index ac9e76e7e60..f1fdbbd2676 100644
--- a/security/kc/Makefile
+++ b/security/kc/Makefile
@@ -11,6 +11,9 @@ MAINTAINER = LEVAI Daniel
# BSD
PERMIT_PACKAGE = Yes
+FLAVORS= yubikey
+FLAVOR?=
+
WANTLIB += c crypto curses edit scrypt util xml2
LIB_DEPENDS = textproc/libxml \
@@ -18,6 +21,15 @@ LIB_DEPENDS = textproc/libxml \
MAKE_ENV += OS_OPENBSD=yes HAVE_LIBSCRYPT=yes
+.if ${FLAVOR:Myubikey}
+WANTLIB += ykpers-1 yubikey
+
+LIB_DEPENDS += security/yubico/yubikey-personalization \
+ security/yubico/yubico-c
+
+MAKE_ENV += HAVE_YUBIKEY=yes
+.endif
+
post-install:
${INSTALL_DATA_DIR} ${PREFIX}/share/doc/kc
${INSTALL} ${WRKBUILD}/Changelog.md ${PREFIX}/share/doc/kc/
diff --git a/security/kc/pkg/MESSAGE b/security/kc/pkg/MESSAGE
index 345fc451266..303ac67cddb 100644
--- a/security/kc/pkg/MESSAGE
+++ b/security/kc/pkg/MESSAGE
@@ -1 +1,3 @@
Please read ${PREFIX}/share/doc/kc/Changelog.md to see why you might not be able to open your database anymore.
+
+Using YubiKey support with the -yubikey flavor requires read/write access to the /dev/usb? and /dev/ugen?.?? devices.
[UPDATE]: security/kc
Hi all, Update kc to 2.5.3 Pretty straightforward diff, tests ran fine. Danieldiff --git a/security/kc/Makefile b/security/kc/Makefile index 9581e04cd2c..ac9e76e7e60 100644 --- a/security/kc/Makefile +++ b/security/kc/Makefile @@ -2,7 +2,7 @@ COMMENT = console based password storing application GH_ACCOUNT = levaidaniel GH_PROJECT = kc -GH_TAGNAME = 2.5.1 +GH_TAGNAME = 2.5.3 CATEGORIES = security diff --git a/security/kc/distinfo b/security/kc/distinfo index a77c2f56933..eb3f0afe9cf 100644 --- a/security/kc/distinfo +++ b/security/kc/distinfo @@ -1,2 +1,2 @@ -SHA256 (kc-2.5.1.tar.gz) = 0CZdohmGwmG9FQKzE1QL/pka+Ll+RKcpbYIv4OLgpjI= -SIZE (kc-2.5.1.tar.gz) = 100143 +SHA256 (kc-2.5.3.tar.gz) = WT2zS/U62Rl8OsH/w3Qt/AOnhIYvCl+t7aa20q0odTk= +SIZE (kc-2.5.3.tar.gz) = 101980
[UPDATE]: security/kc
Hi! Update to kc 2.5.1. This fixes compilation warnings and subsequent erroneous parameter parsing on arm and powerpc (thanks to tb@ for noticing and providing the fix too!). Daniel diff --git a/security/kc/Makefile b/security/kc/Makefile index bb73e24a451..9581e04cd2c 100644 --- a/security/kc/Makefile +++ b/security/kc/Makefile @@ -2,7 +2,7 @@ COMMENT = console based password storing application GH_ACCOUNT = levaidaniel GH_PROJECT = kc -GH_TAGNAME = 2.5.0 +GH_TAGNAME = 2.5.1 CATEGORIES = security diff --git a/security/kc/distinfo b/security/kc/distinfo index 70dbd7a942e..a77c2f56933 100644 --- a/security/kc/distinfo +++ b/security/kc/distinfo @@ -1,2 +1,2 @@ -SHA256 (kc-2.5.0.tar.gz) = e2qyCIwulrcTVvVUz9XSZNE7NouPtnGXLPAxDZRvv64= -SIZE (kc-2.5.0.tar.gz) = 99969 +SHA256 (kc-2.5.1.tar.gz) = 0CZdohmGwmG9FQKzE1QL/pka+Ll+RKcpbYIv4OLgpjI= +SIZE (kc-2.5.1.tar.gz) = 100143
Re: [UPDATE]: security/kc
On Wed, Dec 21, 2022 at 11:26:39PM +, Lévai, Dániel wrote: > Hi! > > This updates kc to 2.5.0. > Please read the Changelog.md file to see what has changed and why you might > not be able to open your older database. > > I removed an unmaintained script (and the README on it), switched to GH_* > variables (easier this way), removed pcre dependency (and thus support), and > removed @ask-update. > Committed, thanks. The instructions in Changelog.md work fine for me and the MESSAGE should be enough for people to be able to recover. For some reason the Makefile diff didn't apply, so I applied it by hand. I also dropped HOMEPAGE since that is set by the GH_ variables.
[UPDATE]: security/kc
Hi!
This updates kc to 2.5.0.
Please read the Changelog.md file to see what has changed and why you might not
be able to open your older database.
I removed an unmaintained script (and the README on it), switched to GH_*
variables (easier this way), removed pcre dependency (and thus support), and
removed @ask-update.
Daniel
diff --git a/security/kc/Makefile b/security/kc/Makefile
index 71ee5b3a0ae..b8d2523c90a 100644
--- a/security/kc/Makefile
+++ b/security/kc/Makefile
@@ -1,10 +1,8 @@
COMMENT = console based password storing application
-V =2.4.2
-DISTNAME = kc-$V
-EXTRACT_SUFX = .tar.bz2
-MASTER_SITES = https://github.com/levaidaniel/kc/releases/download/${V}/
-REVISION = 0
+GH_ACCOUNT = levaidaniel
+GH_PROJECT = kc
+GH_TAGNAME = 2.5.0
CATEGORIES = security
@@ -15,19 +13,16 @@ MAINTAINER =LEVAI Daniel
# BSD
PERMIT_PACKAGE = Yes
-WANTLIB += c crypto curses edit pcre scrypt util xml2
+WANTLIB += c crypto curses edit scrypt util xml2
LIB_DEPENDS = textproc/libxml \
- devel/pcre \
security/libscrypt
-MAKE_ENV +=HAVE_PCRE=yes OS_OPENBSD=yes HAVE_LIBSCRYPT=yes
+MAKE_ENV +=OS_OPENBSD=yes HAVE_LIBSCRYPT=yes
post-install:
- ${INSTALL_DATA_DIR} ${PREFIX}/share/kc
- ${INSTALL} ${WRKBUILD}/pwsafe_to_kc.pl ${PREFIX}/share/kc/
${INSTALL_DATA_DIR} ${PREFIX}/share/doc/kc
- ${INSTALL} ${WRKBUILD}/Changelog ${PREFIX}/share/doc/kc/
+ ${INSTALL} ${WRKBUILD}/Changelog.md ${PREFIX}/share/doc/kc/
.include
diff --git a/security/kc/distinfo b/security/kc/distinfo
index 5a85a457900..70dbd7a942e 100644
--- a/security/kc/distinfo
+++ b/security/kc/distinfo
@@ -1,2 +1,2 @@
-SHA256 (kc-2.4.2.tar.bz2) = PpFoQR8OHwOQE8OwsSXolGt7D+fpLRVvBpyMu0ovimE=
-SIZE (kc-2.4.2.tar.bz2) = 65011
+SHA256 (kc-2.5.0.tar.gz) = e2qyCIwulrcTVvVUz9XSZNE7NouPtnGXLPAxDZRvv64=
+SIZE (kc-2.5.0.tar.gz) = 99969
diff --git a/security/kc/pkg/MESSAGE b/security/kc/pkg/MESSAGE
new file mode 100644
index 000..345fc451266
--- /dev/null
+++ b/security/kc/pkg/MESSAGE
@@ -0,0 +1 @@
+Please read ${PREFIX}/share/doc/kc/Changelog.md to see why you might not be
able to open your database anymore.
diff --git a/security/kc/pkg/PLIST b/security/kc/pkg/PLIST
index 94a73f3dc5a..95289a05e28 100644
--- a/security/kc/pkg/PLIST
+++ b/security/kc/pkg/PLIST
@@ -1,8 +1,4 @@
-@ask-update kc-<2.4 Make sure all your existing kc databases are safely
*dumped* ('dump' command) then read the Changelog in ${PREFIX}/share/doc/kc
after installation
@bin bin/kc
@man man/man1/kc.1
share/doc/kc/
-share/doc/kc/Changelog
-share/doc/pkg-readmes/${PKGSTEM}
-share/kc/
-share/kc/pwsafe_to_kc.pl
+share/doc/kc/Changelog.md
diff --git a/security/kc/pkg/README b/security/kc/pkg/README
deleted file mode 100644
index 46825795305..000
--- a/security/kc/pkg/README
+++ /dev/null
@@ -1,8 +0,0 @@
-+---
-| Running ${PKGSTEM} on OpenBSD
-+---
-
-kc comes with a tiny and simple utility which can convert an exported
-pwsafe database to a kc compatible XML database (that can be imported to
-it later). It is installed under ${PREFIX}/share/kc/. Note that this
-script requires Perl modules provided by the p5-HTML-Parser package.
Re: UPDATE: security/kc
Stuart Henderson @ 2018-04-19T23:04:02 +0200:
Thanks, Stuart,
> On 2018/04/18 18:10, LÉVAI Dániel wrote:
> > Hi!
> >
> > Update to kc, that breaks compatibility with <2.4 kc databases.
> > Please check how I handled it here, I tried to mimic postgresql's way
> > with @ask-update.
[...]
> Since you're upstream would you mind uploading a tar.gz as a
> "release asset" and switching to that please? There's a drag-and-drop
> or file selection box on the releases page (or there are some gists
> floating around if you want to automate it).
>
> That way we aren't at risk of broken auto-generated distfiles
> when github update their software stack.
>
> Ports-wise that involves traditional DISTNAME and MASTER_SITES lines
> instead of GH_*.
I uploaded a new archive (repackaged Github's release tar.gz as tar.bz2)
and I point to that from the Makefile. Is this what you had in mind?
[...]
> > +FLAVORS = scrypt
> > +FLAVOR ?=
> > +
> > +.if ${FLAVOR:Mscrypt}
> > +LIB_DEPENDS += security/libscrypt
> > +MAKE_ENV +=HAVE_LIBSCRYPT=yes
> > +.endif
> > +
>
> It's only a small dep, is there a real advantage to making it optional?
There's no real reason for the FLAVOR other than I didn't want to impose
this on everyone. But you're right, it's a small dep., if it's okay, I
just removed the flavor.
Attached the amended diff (also removed the patch because I've
incorporated it in the new release while there).
Daniel
Index: Makefile
===
RCS file: /cvs/ports/security/kc/Makefile,v
retrieving revision 1.14
diff -u -p -p -u -r1.14 Makefile
--- Makefile29 Dec 2015 19:49:41 - 1.14
+++ Makefile20 Apr 2018 08:52:07 -
@@ -2,29 +2,33 @@
COMMENT = console based password storing application
-GH_ACCOUNT = levaidaniel
-GH_PROJECT = kc
-GH_TAGNAME = 2.3.2
-REVISION = 1
+V =2.4.2
+DISTNAME = kc-$V
+EXTRACT_SUFX = .tar.bz2
+MASTER_SITES = https://github.com/levaidaniel/kc/releases/download/${V}/
CATEGORIES = security
-HOMEPAGE = http://github.com/levaidaniel/${GH_PROJECT}
+HOMEPAGE = http://github.com/levaidaniel/kc/
MAINTAINER = LEVAI Daniel
# BSD
PERMIT_PACKAGE_CDROM = Yes
-WANTLIB += c crypto edit ncursesw pcre pthread xml2
+WANTLIB += c crypto edit ncursesw pcre pthread xml2 scrypt
LIB_DEPENDS = textproc/libxml \
- devel/pcre
+ devel/pcre \
+ security/libscrypt
+
+MAKE_ENV +=HAVE_PCRE=yes OS_OPENBSD=yes HAVE_LIBSCRYPT=yes
-MAKE_ENV +=HAVE_PCRE=yes
post-install:
${INSTALL_DATA_DIR} ${PREFIX}/share/kc
${INSTALL} ${WRKBUILD}/pwsafe_to_kc.pl ${PREFIX}/share/kc/
+ ${INSTALL_DATA_DIR} ${PREFIX}/share/doc/kc
+ ${INSTALL} ${WRKBUILD}/Changelog ${PREFIX}/share/doc/kc/
.include
Index: distinfo
===
RCS file: /cvs/ports/security/kc/distinfo,v
retrieving revision 1.5
diff -u -p -p -u -r1.5 distinfo
--- distinfo24 Dec 2013 12:56:19 - 1.5
+++ distinfo20 Apr 2018 08:52:07 -
@@ -1,2 +1,2 @@
-SHA256 (kc-2.3.2.tar.gz) = 1Ap74wB55M/EI+GqK127Dm8LNInx0OCQzWZyi8Mo/Ng=
-SIZE (kc-2.3.2.tar.gz) = 44779
+SHA256 (kc-2.4.2.tar.bz2) = PpFoQR8OHwOQE8OwsSXolGt7D+fpLRVvBpyMu0ovimE=
+SIZE (kc-2.4.2.tar.bz2) = 65011
Index: pkg/PLIST
===
RCS file: /cvs/ports/security/kc/pkg/PLIST,v
retrieving revision 1.3
diff -u -p -p -u -r1.3 PLIST
--- pkg/PLIST 21 Mar 2013 09:48:45 - 1.3
+++ pkg/PLIST 20 Apr 2018 08:52:07 -
@@ -1,6 +1,9 @@
@comment $OpenBSD: PLIST,v 1.3 2013/03/21 09:48:45 jasper Exp $
+@ask-update kc-<2.4 Make sure all your existing kc databases are safely
*dumped* ('dump' command) then read the Changelog in ${PREFIX}/share/doc/kc
after installation
@bin bin/kc
@man man/man1/kc.1
+share/doc/kc/
+share/doc/kc/Changelog
share/doc/pkg-readmes/${FULLPKGNAME}
share/kc/
share/kc/pwsafe_to_kc.pl
--
LÉVAI Dániel
PGP key ID = 0x83B63A8F
Key fingerprint = DBEC C66B A47A DFA2 792D 650C C69B BE4C 83B6 3A8F
Re: UPDATE: security/kc
On 2018/04/18 18:10, LÉVAI Dániel wrote:
> Hi!
>
> Update to kc, that breaks compatibility with <2.4 kc databases.
> Please check how I handled it here, I tried to mimic postgresql's way
> with @ask-update.
> Index: Makefile
> ===
> RCS file: /cvs/ports/security/kc/Makefile,v
> retrieving revision 1.14
> diff -u -p -p -u -r1.14 Makefile
> --- Makefile 29 Dec 2015 19:49:41 - 1.14
> +++ Makefile 18 Apr 2018 16:06:29 -
> @@ -4,8 +4,7 @@ COMMENT = console based password storing
>
> GH_ACCOUNT = levaidaniel
> GH_PROJECT = kc
> -GH_TAGNAME = 2.3.2
> -REVISION = 1
> +GH_TAGNAME = 2.4.1
Since you're upstream would you mind uploading a tar.gz as a
"release asset" and switching to that please? There's a drag-and-drop
or file selection box on the releases page (or there are some gists
floating around if you want to automate it).
That way we aren't at risk of broken auto-generated distfiles
when github update their software stack.
Ports-wise that involves traditional DISTNAME and MASTER_SITES lines
instead of GH_*.
> CATEGORIES = security
>
> @@ -21,10 +20,21 @@ WANTLIB += c crypto edit ncursesw pcre p
> LIB_DEPENDS =textproc/libxml \
> devel/pcre
>
> -MAKE_ENV += HAVE_PCRE=yes
> +MAKE_ENV += HAVE_PCRE=yes OS_OPENBSD=yes
> +
> +FLAVORS =scrypt
> +FLAVOR ?=
> +
> +.if ${FLAVOR:Mscrypt}
> +LIB_DEPENDS += security/libscrypt
> +MAKE_ENV += HAVE_LIBSCRYPT=yes
> +.endif
> +
It's only a small dep, is there a real advantage to making it optional?
If there is, please mention the flavour in DESCR, otherwise I'd prefer to
have it rolled into a single package.
LIB_DEPENDS with no matching WANTLIB entry is not valid, it will be
stripped by pkg_create with a warning message.
If it's actually static linked then you can *either* list as
BUILD_DEPENDS, *or* list as LIB_DEPENDS + WANTLIB with a comment next
to WANTLIB about it being static linked. I prefer the latter because
there's a higher chance of your port getting updated when that library
is updated. Otherwise you're dependent on manual REVISION bumps to
trigger updates.
> post-install:
> ${INSTALL_DATA_DIR} ${PREFIX}/share/kc
> ${INSTALL} ${WRKBUILD}/pwsafe_to_kc.pl ${PREFIX}/share/kc/
> + ${INSTALL_DATA_DIR} ${PREFIX}/share/doc/kc
> + ${INSTALL} ${WRKBUILD}/Changelog ${PREFIX}/share/doc/kc/
>
> .include
> Index: distinfo
> ===
> RCS file: /cvs/ports/security/kc/distinfo,v
> retrieving revision 1.5
> diff -u -p -p -u -r1.5 distinfo
> --- distinfo 24 Dec 2013 12:56:19 - 1.5
> +++ distinfo 18 Apr 2018 16:06:29 -
> @@ -1,2 +1,2 @@
> -SHA256 (kc-2.3.2.tar.gz) = 1Ap74wB55M/EI+GqK127Dm8LNInx0OCQzWZyi8Mo/Ng=
> -SIZE (kc-2.3.2.tar.gz) = 44779
> +SHA256 (kc-2.4.1.tar.gz) = /+rP1koXzdF1nXsXkwl7CwA9J15klgyYKCepxf2W6Nk=
> +SIZE (kc-2.4.1.tar.gz) = 75169
> Index: patches/patch-Changelog
> ===
> RCS file: patches/patch-Changelog
> diff -N patches/patch-Changelog
> --- /dev/null 1 Jan 1970 00:00:00 -
> +++ patches/patch-Changelog 18 Apr 2018 16:06:29 -
> @@ -0,0 +1,14 @@
> +$OpenBSD$
> +
> +Index: Changelog
> +--- Changelog.orig
> Changelog
> +@@ -43,7 +43,7 @@ Creating '/home/user/.kc/default.kcd'
> + Using '/home/user/.kc/default.kcd' database.
> + New password (empty to cancel):
> + New password again (empty to cancel):
> +- importxml kcdump.xml
> ++ importxml -k kcdump.xml
> + Import OK
> + write
> + Save OK
> Index: pkg/PLIST
> ===
> RCS file: /cvs/ports/security/kc/pkg/PLIST,v
> retrieving revision 1.3
> diff -u -p -p -u -r1.3 PLIST
> --- pkg/PLIST 21 Mar 2013 09:48:45 - 1.3
> +++ pkg/PLIST 18 Apr 2018 16:06:29 -
> @@ -1,6 +1,9 @@
> @comment $OpenBSD: PLIST,v 1.3 2013/03/21 09:48:45 jasper Exp $
> +@ask-update kc-<2.4 Make sure all your existing kc databases are safely
> *dumped* ('dump' command) then read the Changelog in ${PREFIX}/share/doc/kc
> after installation
> @bin bin/kc
> @man man/man1/kc.1
> +share/doc/kc/
> +share/doc/kc/Changelog
> share/doc/pkg-readmes/${FULLPKGNAME}
> share/kc/
> share/kc/pwsafe_to_kc.pl
>
>
>
> --
> LÉVAI Dániel
> PGP key ID = 0x83B63A8F
> Key fingerprint = DBEC C66B A47A DFA2 792D 650C C69B BE4C 83B6 3A8F
>
UPDATE: security/kc
Hi!
Update to kc, that breaks compatibility with <2.4 kc databases.
Please check how I handled it here, I tried to mimic postgresql's way
with @ask-update.
Index: Makefile
===
RCS file: /cvs/ports/security/kc/Makefile,v
retrieving revision 1.14
diff -u -p -p -u -r1.14 Makefile
--- Makefile29 Dec 2015 19:49:41 - 1.14
+++ Makefile18 Apr 2018 16:06:29 -
@@ -4,8 +4,7 @@ COMMENT = console based password storing
GH_ACCOUNT = levaidaniel
GH_PROJECT = kc
-GH_TAGNAME = 2.3.2
-REVISION = 1
+GH_TAGNAME = 2.4.1
CATEGORIES = security
@@ -21,10 +20,21 @@ WANTLIB += c crypto edit ncursesw pcre p
LIB_DEPENDS = textproc/libxml \
devel/pcre
-MAKE_ENV +=HAVE_PCRE=yes
+MAKE_ENV +=HAVE_PCRE=yes OS_OPENBSD=yes
+
+FLAVORS = scrypt
+FLAVOR ?=
+
+.if ${FLAVOR:Mscrypt}
+LIB_DEPENDS += security/libscrypt
+MAKE_ENV +=HAVE_LIBSCRYPT=yes
+.endif
+
post-install:
${INSTALL_DATA_DIR} ${PREFIX}/share/kc
${INSTALL} ${WRKBUILD}/pwsafe_to_kc.pl ${PREFIX}/share/kc/
+ ${INSTALL_DATA_DIR} ${PREFIX}/share/doc/kc
+ ${INSTALL} ${WRKBUILD}/Changelog ${PREFIX}/share/doc/kc/
.include
Index: distinfo
===
RCS file: /cvs/ports/security/kc/distinfo,v
retrieving revision 1.5
diff -u -p -p -u -r1.5 distinfo
--- distinfo24 Dec 2013 12:56:19 - 1.5
+++ distinfo18 Apr 2018 16:06:29 -
@@ -1,2 +1,2 @@
-SHA256 (kc-2.3.2.tar.gz) = 1Ap74wB55M/EI+GqK127Dm8LNInx0OCQzWZyi8Mo/Ng=
-SIZE (kc-2.3.2.tar.gz) = 44779
+SHA256 (kc-2.4.1.tar.gz) = /+rP1koXzdF1nXsXkwl7CwA9J15klgyYKCepxf2W6Nk=
+SIZE (kc-2.4.1.tar.gz) = 75169
Index: patches/patch-Changelog
===
RCS file: patches/patch-Changelog
diff -N patches/patch-Changelog
--- /dev/null 1 Jan 1970 00:00:00 -
+++ patches/patch-Changelog 18 Apr 2018 16:06:29 -
@@ -0,0 +1,14 @@
+$OpenBSD$
+
+Index: Changelog
+--- Changelog.orig
Changelog
+@@ -43,7 +43,7 @@ Creating '/home/user/.kc/default.kcd'
+ Using '/home/user/.kc/default.kcd' database.
+ New password (empty to cancel):
+ New password again (empty to cancel):
+- importxml kcdump.xml
++ importxml -k kcdump.xml
+ Import OK
+ write
+ Save OK
Index: pkg/PLIST
===
RCS file: /cvs/ports/security/kc/pkg/PLIST,v
retrieving revision 1.3
diff -u -p -p -u -r1.3 PLIST
--- pkg/PLIST 21 Mar 2013 09:48:45 - 1.3
+++ pkg/PLIST 18 Apr 2018 16:06:29 -
@@ -1,6 +1,9 @@
@comment $OpenBSD: PLIST,v 1.3 2013/03/21 09:48:45 jasper Exp $
+@ask-update kc-<2.4 Make sure all your existing kc databases are safely
*dumped* ('dump' command) then read the Changelog in ${PREFIX}/share/doc/kc
after installation
@bin bin/kc
@man man/man1/kc.1
+share/doc/kc/
+share/doc/kc/Changelog
share/doc/pkg-readmes/${FULLPKGNAME}
share/kc/
share/kc/pwsafe_to_kc.pl
--
LÉVAI Dániel
PGP key ID = 0x83B63A8F
Key fingerprint = DBEC C66B A47A DFA2 792D 650C C69B BE4C 83B6 3A8F
Re: UPDATE: security/kc 2.3.2
On h, dec 23, 2013 at 18:51:36 +0100, Jérémie Courrèges-Anglas wrote: > LEVAI Daniel writes: [...] > > This seems fine, but why did you remove the test target? > > I did not, "test" is the default for TEST_TARGET when not modified by > some module. If a port doesn't have a test suite then NO_TEST = Yes > should be used. Ah, I see; makes sense. Thanks, I'm totally okay with the (your) last diff. Daniel -- LÉVAI Dániel PGP key ID = 0x83B63A8F Key fingerprint = DBEC C66B A47A DFA2 792D 650C C69B BE4C 83B6 3A8F
Re: UPDATE: security/kc 2.3.2
LEVAI Daniel writes: > On h, dec 23, 2013 at 18:20:12 +0100, Jérémie Courrèges-Anglas wrote: >> "Dmitrij D. Czarkoff" writes: >> >> > LEVAI Daniel said: >> >> I don't mind having the pwsafe convert utility around, I just tought >> >> that generally the expectation is that if something gets installed, then >> >> it should (or supposed to) work :) If it's enough (from the user point >> >> of view) that perl will warn the user that some modules are necessary >> >> for running said program, then I'm okay with installing it henceforward. >> >> If this is the case, I guess the pkg-readme could also stay, but with >> >> some modifications that mention the perl module dependency. Is this an >> >> acceptable standard in the ports tree? >> > >> > I would drop the readme from the patch and either drop it from PLIST or >> > (if it is worth having) make a subpackage. >> >> I don't think the complexity of subpackages are worth it, I'd just ship >> the script as is, with a note in the readme. > > > This seems fine, but why did you remove the test target? I did not, "test" is the default for TEST_TARGET when not modified by some module. If a port doesn't have a test suite then NO_TEST = Yes should be used. Cheers, -- jca | PGP: 0x06A11494 / 61DB D9A0 00A4 67CF 2A90 8961 6191 8FBF 06A1 1494
Re: UPDATE: security/kc 2.3.2
On h, dec 23, 2013 at 18:20:12 +0100, Jérémie Courrèges-Anglas wrote: > "Dmitrij D. Czarkoff" writes: > > > LEVAI Daniel said: > >> I don't mind having the pwsafe convert utility around, I just tought > >> that generally the expectation is that if something gets installed, then > >> it should (or supposed to) work :) If it's enough (from the user point > >> of view) that perl will warn the user that some modules are necessary > >> for running said program, then I'm okay with installing it henceforward. > >> If this is the case, I guess the pkg-readme could also stay, but with > >> some modifications that mention the perl module dependency. Is this an > >> acceptable standard in the ports tree? > > > > I would drop the readme from the patch and either drop it from PLIST or > > (if it is worth having) make a subpackage. > > I don't think the complexity of subpackages are worth it, I'd just ship > the script as is, with a note in the readme. This seems fine, but why did you remove the test target? Daniel -- LÉVAI Dániel PGP key ID = 0x83B63A8F Key fingerprint = DBEC C66B A47A DFA2 792D 650C C69B BE4C 83B6 3A8F
Re: UPDATE: security/kc 2.3.2
"Dmitrij D. Czarkoff" writes:
> LEVAI Daniel said:
>> I don't mind having the pwsafe convert utility around, I just tought
>> that generally the expectation is that if something gets installed, then
>> it should (or supposed to) work :) If it's enough (from the user point
>> of view) that perl will warn the user that some modules are necessary
>> for running said program, then I'm okay with installing it henceforward.
>> If this is the case, I guess the pkg-readme could also stay, but with
>> some modifications that mention the perl module dependency. Is this an
>> acceptable standard in the ports tree?
>
> I would drop the readme from the patch and either drop it from PLIST or
> (if it is worth having) make a subpackage.
I don't think the complexity of subpackages are worth it, I'd just ship
the script as is, with a note in the readme.
Index: Makefile
===
RCS file: /cvs/ports/security/kc/Makefile,v
retrieving revision 1.7
diff -u -p -r1.7 Makefile
--- Makefile7 Aug 2013 21:32:34 - 1.7
+++ Makefile23 Dec 2013 17:07:14 -
@@ -2,12 +2,15 @@
COMMENT = console based password storing application
-DISTNAME = kc-2.3.0
-REVISION = 0
-CATEGORIES =security
+GH_VER = 2.3.2
+PROJECT = kc
+DISTNAME = ${PROJECT}-${GH_VER}
+CATEGORIES = security
-HOMEPAGE = https://code.google.com/p/keychain
-MASTER_SITES = https://keychain.googlecode.com/files/
+HOMEPAGE = http://github.com/levaidaniel/${PROJECT}
+MASTER_SITES = https://github.com/levaidaniel/${PROJECT}/archive/
+
+DISTFILES =${DISTNAME}{${GH_VER}}${EXTRACT_SUFX}
MAINTAINER = LEVAI Daniel
@@ -19,13 +22,7 @@ WANTLIB =c crypto edit ncursesw xml2 pc
LIB_DEPENDS = textproc/libxml \
devel/pcre
-# only required for the pwsafe_to_kc.pl utility,
-# and not for kc itself.
-RUN_DEPENDS = www/p5-HTML-Parser
-
MAKE_ENV +=HAVE_PCRE=yes
-
-TEST_TARGET =test
post-install:
${INSTALL_DATA_DIR} ${PREFIX}/share/kc
Index: distinfo
===
RCS file: /cvs/ports/security/kc/distinfo,v
retrieving revision 1.4
diff -u -p -r1.4 distinfo
--- distinfo21 Mar 2013 09:48:45 - 1.4
+++ distinfo21 Dec 2013 22:03:27 -
@@ -1,2 +1,2 @@
-SHA256 (kc-2.3.0.tar.gz) = SNp9q8TaMX7ACQLN2BGwsEAIkjoYsvKiGUjAQQNWsq4=
-SIZE (kc-2.3.0.tar.gz) = 43625
+SHA256 (kc-2.3.2.tar.gz) = 1Ap74wB55M/EI+GqK127Dm8LNInx0OCQzWZyi8Mo/Ng=
+SIZE (kc-2.3.2.tar.gz) = 44779
Index: pkg/README
===
RCS file: /cvs/ports/security/kc/pkg/README,v
retrieving revision 1.1
diff -u -p -r1.1 README
--- pkg/README 25 Jan 2013 11:09:20 - 1.1
+++ pkg/README 23 Dec 2013 17:18:52 -
@@ -4,6 +4,7 @@ $OpenBSD: README,v 1.1 2013/01/25 11:09:
| Running ${FULLPKGNAME} on OpenBSD
+---
-kc comes with a tiny and simple utility which can convert an exported pwsafe
-database to a kc compatible XML database (that can be imported to it later).
-It is installed under ${PREFIX}/share/kc/
+kc comes with a tiny and simple utility which can convert an exported
+pwsafe database to a kc compatible XML database (that can be imported to
+it later). It is installed under ${PREFIX}/share/kc/. Note that this
+script requires Perl modules provided by the p5-HTML-Parser package.
--
jca | PGP: 0x06A11494 / 61DB D9A0 00A4 67CF 2A90 8961 6191 8FBF 06A1 1494
Re: UPDATE: security/kc 2.3.2
LEVAI Daniel said: > I don't mind having the pwsafe convert utility around, I just tought > that generally the expectation is that if something gets installed, then > it should (or supposed to) work :) If it's enough (from the user point > of view) that perl will warn the user that some modules are necessary > for running said program, then I'm okay with installing it henceforward. > If this is the case, I guess the pkg-readme could also stay, but with > some modifications that mention the perl module dependency. Is this an > acceptable standard in the ports tree? I would drop the readme from the patch and either drop it from PLIST or (if it is worth having) make a subpackage. -- Dmitrij D. Czarkoff
Re: UPDATE: security/kc 2.3.2
On v, dec 22, 2013 at 00:48:47 +0100, Jérémie Courrèges-Anglas wrote: > LEVAI Daniel writes: > > > On szo, dec 14, 2013 at 15:25:47 +0100, LEVAI Daniel wrote: > >> Hi! > >> > >> Here is an update to kc. > >> The development transitioned to github. > >> Also, do not install pwsafe...pl, and remove its dependencies. The > >> utility is still available in the source and on the project website, but > >> it is ridiculous how many stuff is needed for p5-HTML-Parser, and none > >> of them are justified to be installed with kc itself. > > > > New diff. Remove the pkg-readme also from the PLIST, and use the newer > > style for github distfiles. > > Alternately you could still install pwsafe_to_kc.pl but drop the > run-depends, what do you think? Otherwise ok. [...] I don't mind having the pwsafe convert utility around, I just tought that generally the expectation is that if something gets installed, then it should (or supposed to) work :) If it's enough (from the user point of view) that perl will warn the user that some modules are necessary for running said program, then I'm okay with installing it henceforward. If this is the case, I guess the pkg-readme could also stay, but with some modifications that mention the perl module dependency. Is this an acceptable standard in the ports tree? Daniel -- LÉVAI Dániel PGP key ID = 0x83B63A8F Key fingerprint = DBEC C66B A47A DFA2 792D 650C C69B BE4C 83B6 3A8F
Re: UPDATE: security/kc 2.3.2
LEVAI Daniel writes:
> On szo, dec 14, 2013 at 15:25:47 +0100, LEVAI Daniel wrote:
>> Hi!
>>
>> Here is an update to kc.
>> The development transitioned to github.
>> Also, do not install pwsafe...pl, and remove its dependencies. The
>> utility is still available in the source and on the project website, but
>> it is ridiculous how many stuff is needed for p5-HTML-Parser, and none
>> of them are justified to be installed with kc itself.
>
> New diff. Remove the pkg-readme also from the PLIST, and use the newer
> style for github distfiles.
Alternately you could still install pwsafe_to_kc.pl but drop the
run-depends, what do you think? Otherwise ok.
> Index: Makefile
> ===
> RCS file: /cvs/ports/security/kc/Makefile,v
> retrieving revision 1.6
> diff -u -p -r1.6 Makefile
> --- Makefile 21 Mar 2013 09:48:45 - 1.6
> +++ Makefile 15 Dec 2013 10:20:30 -
> @@ -2,11 +2,15 @@
>
> COMMENT =console based password storing application
>
> -DISTNAME = kc-2.3.0
> -CATEGORIES =security
> +GH_VER = 2.3.2
> +PROJECT =kc
> +DISTNAME = ${PROJECT}-${GH_VER}
> +CATEGORIES = security
>
> -HOMEPAGE = http://code.google.com/p/keychain
> -MASTER_SITES = http://keychain.googlecode.com/files/
> +HOMEPAGE = http://github.com/levaidaniel/${PROJECT}
> +MASTER_SITES = https://github.com/levaidaniel/${PROJECT}/archive/
> +
> +DISTFILES = ${DISTNAME}{${GH_VER}}${EXTRACT_SUFX}
>
> MAINTAINER = LEVAI Daniel
>
> @@ -18,16 +22,8 @@ WANTLIB = c crypto edit ncursesw xml2 pc
> LIB_DEPENDS =textproc/libxml \
> devel/pcre
>
> -# only required for the pwsafe_to_kc.pl utility,
> -# and not for kc itself.
> -RUN_DEPENDS =www/p5-HTML-Parser
> -
> MAKE_ENV += HAVE_PCRE=yes
>
> TEST_TARGET =test
> -
> -post-install:
> - ${INSTALL_DATA_DIR} ${PREFIX}/share/kc
> - ${INSTALL} ${WRKBUILD}/pwsafe_to_kc.pl ${PREFIX}/share/kc/
>
> .include
> Index: distinfo
> ===
> RCS file: /cvs/ports/security/kc/distinfo,v
> retrieving revision 1.4
> diff -u -p -r1.4 distinfo
> --- distinfo 21 Mar 2013 09:48:45 - 1.4
> +++ distinfo 15 Dec 2013 10:20:30 -
> @@ -1,2 +1,2 @@
> -SHA256 (kc-2.3.0.tar.gz) = SNp9q8TaMX7ACQLN2BGwsEAIkjoYsvKiGUjAQQNWsq4=
> -SIZE (kc-2.3.0.tar.gz) = 43625
> +SHA256 (kc-2.3.2.tar.gz) = 1Ap74wB55M/EI+GqK127Dm8LNInx0OCQzWZyi8Mo/Ng=
> +SIZE (kc-2.3.2.tar.gz) = 44779
> Index: pkg/PLIST
> ===
> RCS file: /cvs/ports/security/kc/pkg/PLIST,v
> retrieving revision 1.3
> diff -u -p -r1.3 PLIST
> --- pkg/PLIST 21 Mar 2013 09:48:45 - 1.3
> +++ pkg/PLIST 15 Dec 2013 10:20:30 -
> @@ -1,6 +1,3 @@
> -@comment $OpenBSD: PLIST,v 1.3 2013/03/21 09:48:45 jasper Exp $
> +@comment $OpenBSD$
> @bin bin/kc
> @man man/man1/kc.1
> -share/doc/pkg-readmes/${FULLPKGNAME}
> -share/kc/
> -share/kc/pwsafe_to_kc.pl
> Index: pkg/README
> ===
> RCS file: pkg/README
> diff -N pkg/README
> --- pkg/README25 Jan 2013 11:09:20 - 1.1
> +++ /dev/null 1 Jan 1970 00:00:00 -
> @@ -1,9 +0,0 @@
> -$OpenBSD: README,v 1.1 2013/01/25 11:09:20 jasper Exp $
> -
> -+---
> -| Running ${FULLPKGNAME} on OpenBSD
> -+---
> -
> -kc comes with a tiny and simple utility which can convert an exported pwsafe
> -database to a kc compatible XML database (that can be imported to it later).
> -It is installed under ${PREFIX}/share/kc/
>
>
>
>
> Daniel
--
jca | PGP: 0x06A11494 / 61DB D9A0 00A4 67CF 2A90 8961 6191 8FBF 06A1 1494
Re: UPDATE: security/kc 2.3.2
On v, dec 15, 2013 at 11:34:20 +0100, LEVAI Daniel wrote: > On szo, dec 14, 2013 at 15:25:47 +0100, LEVAI Daniel wrote: > > Hi! > > > > Here is an update to kc. > > The development transitioned to github. > > Also, do not install pwsafe...pl, and remove its dependencies. The > > utility is still available in the source and on the project website, but > > it is ridiculous how many stuff is needed for p5-HTML-Parser, and none > > of them are justified to be installed with kc itself. > > New diff. Remove the pkg-readme also from the PLIST, and use the newer > style for github distfiles. [...] Ping? Daniel -- LÉVAI Dániel PGP key ID = 0x83B63A8F Key fingerprint = DBEC C66B A47A DFA2 792D 650C C69B BE4C 83B6 3A8F
Re: UPDATE: security/kc 2.3.2
On szo, dec 14, 2013 at 15:25:47 +0100, LEVAI Daniel wrote:
> Hi!
>
> Here is an update to kc.
> The development transitioned to github.
> Also, do not install pwsafe...pl, and remove its dependencies. The
> utility is still available in the source and on the project website, but
> it is ridiculous how many stuff is needed for p5-HTML-Parser, and none
> of them are justified to be installed with kc itself.
New diff. Remove the pkg-readme also from the PLIST, and use the newer
style for github distfiles.
Index: Makefile
===
RCS file: /cvs/ports/security/kc/Makefile,v
retrieving revision 1.6
diff -u -p -r1.6 Makefile
--- Makefile21 Mar 2013 09:48:45 - 1.6
+++ Makefile15 Dec 2013 10:20:30 -
@@ -2,11 +2,15 @@
COMMENT = console based password storing application
-DISTNAME = kc-2.3.0
-CATEGORIES =security
+GH_VER = 2.3.2
+PROJECT = kc
+DISTNAME = ${PROJECT}-${GH_VER}
+CATEGORIES = security
-HOMEPAGE = http://code.google.com/p/keychain
-MASTER_SITES = http://keychain.googlecode.com/files/
+HOMEPAGE = http://github.com/levaidaniel/${PROJECT}
+MASTER_SITES = https://github.com/levaidaniel/${PROJECT}/archive/
+
+DISTFILES =${DISTNAME}{${GH_VER}}${EXTRACT_SUFX}
MAINTAINER = LEVAI Daniel
@@ -18,16 +22,8 @@ WANTLIB =c crypto edit ncursesw xml2 pc
LIB_DEPENDS = textproc/libxml \
devel/pcre
-# only required for the pwsafe_to_kc.pl utility,
-# and not for kc itself.
-RUN_DEPENDS = www/p5-HTML-Parser
-
MAKE_ENV +=HAVE_PCRE=yes
TEST_TARGET =test
-
-post-install:
- ${INSTALL_DATA_DIR} ${PREFIX}/share/kc
- ${INSTALL} ${WRKBUILD}/pwsafe_to_kc.pl ${PREFIX}/share/kc/
.include
Index: distinfo
===
RCS file: /cvs/ports/security/kc/distinfo,v
retrieving revision 1.4
diff -u -p -r1.4 distinfo
--- distinfo21 Mar 2013 09:48:45 - 1.4
+++ distinfo15 Dec 2013 10:20:30 -
@@ -1,2 +1,2 @@
-SHA256 (kc-2.3.0.tar.gz) = SNp9q8TaMX7ACQLN2BGwsEAIkjoYsvKiGUjAQQNWsq4=
-SIZE (kc-2.3.0.tar.gz) = 43625
+SHA256 (kc-2.3.2.tar.gz) = 1Ap74wB55M/EI+GqK127Dm8LNInx0OCQzWZyi8Mo/Ng=
+SIZE (kc-2.3.2.tar.gz) = 44779
Index: pkg/PLIST
===
RCS file: /cvs/ports/security/kc/pkg/PLIST,v
retrieving revision 1.3
diff -u -p -r1.3 PLIST
--- pkg/PLIST 21 Mar 2013 09:48:45 - 1.3
+++ pkg/PLIST 15 Dec 2013 10:20:30 -
@@ -1,6 +1,3 @@
-@comment $OpenBSD: PLIST,v 1.3 2013/03/21 09:48:45 jasper Exp $
+@comment $OpenBSD$
@bin bin/kc
@man man/man1/kc.1
-share/doc/pkg-readmes/${FULLPKGNAME}
-share/kc/
-share/kc/pwsafe_to_kc.pl
Index: pkg/README
===
RCS file: pkg/README
diff -N pkg/README
--- pkg/README 25 Jan 2013 11:09:20 - 1.1
+++ /dev/null 1 Jan 1970 00:00:00 -
@@ -1,9 +0,0 @@
-$OpenBSD: README,v 1.1 2013/01/25 11:09:20 jasper Exp $
-
-+---
-| Running ${FULLPKGNAME} on OpenBSD
-+---
-
-kc comes with a tiny and simple utility which can convert an exported pwsafe
-database to a kc compatible XML database (that can be imported to it later).
-It is installed under ${PREFIX}/share/kc/
Daniel
--
LÉVAI Dániel
PGP key ID = 0x83B63A8F
Key fingerprint = DBEC C66B A47A DFA2 792D 650C C69B BE4C 83B6 3A8F
UPDATE: security/kc 2.3.2
Hi!
Here is an update to kc.
The development transitioned to github.
Also, do not install pwsafe...pl, and remove its dependencies. The
utility is still available in the source and on the project website, but
it is ridiculous how many stuff is needed for p5-HTML-Parser, and none
of them are justified to be installed with kc itself.
Index: Makefile
===
RCS file: /cvs/ports/security/kc/Makefile,v
retrieving revision 1.6
diff -u -p -p -u -r1.6 Makefile
--- Makefile21 Mar 2013 09:48:45 - 1.6
+++ Makefile14 Dec 2013 14:22:32 -
@@ -2,11 +2,13 @@
COMMENT = console based password storing application
-DISTNAME = kc-2.3.0
+V =2.3.2
+PROJECT = kc
+DISTNAME = ${PROJECT}-${V}
CATEGORIES =security
-HOMEPAGE = http://code.google.com/p/keychain
-MASTER_SITES = http://keychain.googlecode.com/files/
+HOMEPAGE = http://github.com/levaidaniel/kc
+MASTER_SITES =
http://github.com/levaidaniel/${PROJECT}/archive/${V}.tar.gz?dummy=/
MAINTAINER = LEVAI Daniel
@@ -18,16 +20,8 @@ WANTLIB =c crypto edit ncursesw xml2 pc
LIB_DEPENDS = textproc/libxml \
devel/pcre
-# only required for the pwsafe_to_kc.pl utility,
-# and not for kc itself.
-RUN_DEPENDS = www/p5-HTML-Parser
-
MAKE_ENV +=HAVE_PCRE=yes
TEST_TARGET =test
-
-post-install:
- ${INSTALL_DATA_DIR} ${PREFIX}/share/kc
- ${INSTALL} ${WRKBUILD}/pwsafe_to_kc.pl ${PREFIX}/share/kc/
.include
Index: distinfo
===
RCS file: /cvs/ports/security/kc/distinfo,v
retrieving revision 1.4
diff -u -p -p -u -r1.4 distinfo
--- distinfo21 Mar 2013 09:48:45 - 1.4
+++ distinfo14 Dec 2013 14:22:32 -
@@ -1,2 +1,2 @@
-SHA256 (kc-2.3.0.tar.gz) = SNp9q8TaMX7ACQLN2BGwsEAIkjoYsvKiGUjAQQNWsq4=
-SIZE (kc-2.3.0.tar.gz) = 43625
+SHA256 (kc-2.3.2.tar.gz) = 1Ap74wB55M/EI+GqK127Dm8LNInx0OCQzWZyi8Mo/Ng=
+SIZE (kc-2.3.2.tar.gz) = 44779
Index: pkg/PLIST
===
RCS file: /cvs/ports/security/kc/pkg/PLIST,v
retrieving revision 1.3
diff -u -p -p -u -r1.3 PLIST
--- pkg/PLIST 21 Mar 2013 09:48:45 - 1.3
+++ pkg/PLIST 14 Dec 2013 14:22:32 -
@@ -2,5 +2,3 @@
@bin bin/kc
@man man/man1/kc.1
share/doc/pkg-readmes/${FULLPKGNAME}
-share/kc/
-share/kc/pwsafe_to_kc.pl
Index: pkg/README
===
RCS file: pkg/README
diff -N pkg/README
--- pkg/README 25 Jan 2013 11:09:20 - 1.1
+++ /dev/null 1 Jan 1970 00:00:00 -
@@ -1,9 +0,0 @@
-$OpenBSD: README,v 1.1 2013/01/25 11:09:20 jasper Exp $
-
-+---
-| Running ${FULLPKGNAME} on OpenBSD
-+---
-
-kc comes with a tiny and simple utility which can convert an exported pwsafe
-database to a kc compatible XML database (that can be imported to it later).
-It is installed under ${PREFIX}/share/kc/
Daniel
--
LÉVAI Dániel
PGP key ID = 0x83B63A8F
Key fingerprint = DBEC C66B A47A DFA2 792D 650C C69B BE4C 83B6 3A8F
UPDATE: security/kc -> 2.2.1
Hi!
Here is an update to security/kc.
A patch file was removed, WANTLIB was shortened, added a RUN_DEPEND,
simplified MAKE_ENV, added a pkg MESSAGE, man page is now installed to
the right place.
Tested only on i386.
Index: Makefile
===
RCS file: /cvs/ports/security/kc/Makefile,v
retrieving revision 1.3
diff -p -u -r1.3 Makefile
--- Makefile15 Oct 2012 15:18:33 - 1.3
+++ Makefile16 Jan 2013 10:39:36 -
@@ -2,7 +2,7 @@
COMMENT = console based password storing application
-DISTNAME = kc-2.1.6
+DISTNAME = kc-2.2.1
CATEGORIES =security
HOMEPAGE = http://code.google.com/p/keychain
@@ -16,11 +16,19 @@ PERMIT_PACKAGE_FTP =Yes
PERMIT_DISTFILES_CDROM = Yes
PERMIT_DISTFILES_FTP = Yes
-WANTLIB = c ssl crypto edit ncursesw xml2 pcre
+WANTLIB = c crypto edit ncursesw xml2 pcre
LIB_DEPENDS = textproc/libxml \
devel/pcre
-MAKE_ENV +=HAVE_PCRE=yes CC="${CC}"
+# only required for the pwsafe_convert.pl utility,
+# and not for kc itself.
+RUN_DEPENDS = www/p5-HTML-Parser
+
+MAKE_ENV +=HAVE_PCRE=yes
+
+post-install:
+ ${INSTALL_DATA_DIR} ${PREFIX}/share/kc
+ ${INSTALL} ${WRKBUILD}/pwsafe_convert.pl ${PREFIX}/share/kc/
.include
Index: distinfo
===
RCS file: /cvs/ports/security/kc/distinfo,v
retrieving revision 1.2
diff -p -u -r1.2 distinfo
--- distinfo6 Sep 2012 19:22:53 - 1.2
+++ distinfo16 Jan 2013 10:39:36 -
@@ -1,2 +1,2 @@
-SHA256 (kc-2.1.6.tar.gz) = QUtzhaZJ1s+D4S1KrgRd4RNJ9BVt4NibjFQ2g7By830=
-SIZE (kc-2.1.6.tar.gz) = 22276
+SHA256 (kc-2.2.1.tar.gz) = rbZbWiNOSUcvPLoub4WVJ1yr7SlajzDamVsR659bsO4=
+SIZE (kc-2.2.1.tar.gz) = 31344
Index: patches/patch-kc_1
===
RCS file: patches/patch-kc_1
diff -N patches/patch-kc_1
--- patches/patch-kc_1 6 Sep 2012 19:22:53 - 1.1
+++ /dev/null 1 Jan 1970 00:00:00 -
@@ -1,15 +0,0 @@
-$OpenBSD: patch-kc_1,v 1.1 2012/09/06 19:22:53 sthen Exp $
-mandoc -Tlint told me to fix this.
kc.1.orig Thu Sep 6 20:30:51 2012
-+++ kc.1 Thu Sep 6 20:31:07 2012
-@@ -80,9 +80,9 @@ Display version.
- Display help.
- .El
- .Ss COMMANDS
--.Bl -tag -offset ||| -width |
- .Pp
- These commands can be used in the CLI:
-+.Bl -tag -offset ||| -width |
- .It Cm new Op name
- Create a new key in the current keychain. If
- .Ar name
Index: pkg/MESSAGE
===
RCS file: pkg/MESSAGE
diff -N pkg/MESSAGE
--- /dev/null 1 Jan 1970 00:00:00 -
+++ pkg/MESSAGE 16 Jan 2013 10:39:36 -
@@ -0,0 +1,3 @@
+kc comes with a tiny and simple utility which can convert an exported pwsafe
+database to a kc compatible XML database (that can be imported to it later).
+It is installed under ${PREFIX}/share/kc/
Index: pkg/PLIST
===
RCS file: /cvs/ports/security/kc/pkg/PLIST,v
retrieving revision 1.1.1.1
diff -p -u -r1.1.1.1 PLIST
--- pkg/PLIST 25 Apr 2012 14:04:06 - 1.1.1.1
+++ pkg/PLIST 16 Jan 2013 10:39:36 -
@@ -1,3 +1,5 @@
-@comment $OpenBSD: PLIST,v 1.1.1.1 2012/04/25 14:04:06 okan Exp $
+@comment $OpenBSD$
@bin bin/kc
-man/cat1/kc.1
+@man man/man1/kc.1
+share/kc/
+share/kc/pwsafe_convert.pl
Daniel
--
LÉVAI Dániel
PGP key ID = 0x83B63A8F
Key fingerprint = DBEC C66B A47A DFA2 792D 650C C69B BE4C 83B6 3A8F
UPDATE: security/kc -> 2.2.0
Hi!
Here is an update to security/kc:
Index: Makefile
===
RCS file: /cvs/ports/security/kc/Makefile,v
retrieving revision 1.3
diff -p -u -r1.3 Makefile
--- Makefile15 Oct 2012 15:18:33 - 1.3
+++ Makefile10 Jan 2013 21:52:54 -
@@ -2,7 +2,7 @@
COMMENT = console based password storing application
-DISTNAME = kc-2.1.6
+DISTNAME = kc-2.2.0
CATEGORIES =security
HOMEPAGE = http://code.google.com/p/keychain
@@ -21,6 +21,14 @@ WANTLIB =c ssl crypto edit ncursesw xml
LIB_DEPENDS = textproc/libxml \
devel/pcre
+# only required for the pwsafe_convert.pl utility,
+# and not for kc itself.
+RUN_DEPENDS = www/p5-HTML-Parser
+
MAKE_ENV +=HAVE_PCRE=yes CC="${CC}"
+
+post-install:
+ ${INSTALL_DATA_DIR} ${PREFIX}/share/kc
+ ${INSTALL} ${WRKBUILD}/pwsafe_convert.pl ${PREFIX}/share/kc/
.include
Index: distinfo
===
RCS file: /cvs/ports/security/kc/distinfo,v
retrieving revision 1.2
diff -p -u -r1.2 distinfo
--- distinfo6 Sep 2012 19:22:53 - 1.2
+++ distinfo10 Jan 2013 21:52:54 -
@@ -1,2 +1,2 @@
-SHA256 (kc-2.1.6.tar.gz) = QUtzhaZJ1s+D4S1KrgRd4RNJ9BVt4NibjFQ2g7By830=
-SIZE (kc-2.1.6.tar.gz) = 22276
+SHA256 (kc-2.2.0.tar.gz) = KXnAnby2JJdafNbadb0dqsQ+JfhMNfD3fYt/3QMGBig=
+SIZE (kc-2.2.0.tar.gz) = 31291
Index: patches/patch-kc_1
===
RCS file: patches/patch-kc_1
diff -N patches/patch-kc_1
--- patches/patch-kc_1 6 Sep 2012 19:22:53 - 1.1
+++ /dev/null 1 Jan 1970 00:00:00 -
@@ -1,15 +0,0 @@
-$OpenBSD: patch-kc_1,v 1.1 2012/09/06 19:22:53 sthen Exp $
-mandoc -Tlint told me to fix this.
kc.1.orig Thu Sep 6 20:30:51 2012
-+++ kc.1 Thu Sep 6 20:31:07 2012
-@@ -80,9 +80,9 @@ Display version.
- Display help.
- .El
- .Ss COMMANDS
--.Bl -tag -offset ||| -width |
- .Pp
- These commands can be used in the CLI:
-+.Bl -tag -offset ||| -width |
- .It Cm new Op name
- Create a new key in the current keychain. If
- .Ar name
Index: pkg/MESSAGE
===
RCS file: pkg/MESSAGE
diff -N pkg/MESSAGE
--- /dev/null 1 Jan 1970 00:00:00 -
+++ pkg/MESSAGE 10 Jan 2013 21:52:54 -
@@ -0,0 +1,3 @@
+kc comes with a tiny and simple utility which can convert an exported pwsafe
+database to a kc compatible XML database (that can be imported to it later).
+It is installed under ${PREFIX}/share/kc/
Index: pkg/PLIST
===
RCS file: /cvs/ports/security/kc/pkg/PLIST,v
retrieving revision 1.1.1.1
diff -p -u -r1.1.1.1 PLIST
--- pkg/PLIST 25 Apr 2012 14:04:06 - 1.1.1.1
+++ pkg/PLIST 10 Jan 2013 21:52:54 -
@@ -1,3 +1,5 @@
-@comment $OpenBSD: PLIST,v 1.1.1.1 2012/04/25 14:04:06 okan Exp $
+@comment $OpenBSD$
@bin bin/kc
-man/cat1/kc.1
+@man man/man1/kc.1
+share/kc/
+share/kc/pwsafe_convert.pl
Daniel
--
LÉVAI Dániel
PGP key ID = 0x83B63A8F
Key fingerprint = DBEC C66B A47A DFA2 792D 650C C69B BE4C 83B6 3A8F
