security/fprintd is a port of http://www.freedesktop.org/wiki/Software/fprint/fprintd/
Quoting from that page: "fprintd is a D-Bus daemon that offers libfprint functionality over the D-Bus interprocess communication bus. By adding this daemon layer above libfprint, we solve various problems related to multiple applications simulatenously competing for fingerprint readers."
The port is ready in redports: http://www.freshports.org/security/fprintd
That was wrong; it is ready in https://redports.org/buildarchive/20140815111701-48039/
Martin, you'll need to provide a shar as an attachment. It should be easy to create, so just attach it.
Created attachment 145829 [details]
shar file of security/fprintd, as used in redports
this is outdated:
it's tar:xz now
And the redports link is showing "leftovers" ?
Created attachment 145832 [details]
fixed shar: USE_XZ -> tar:xz
This is hard... a new shar with fixed xz is attached, however -
Regarding the "leftovers", I had looked at them and had concluded they were caused by the following:
=== Checking filesystem state
list of files present before this port was installed but missing after it was deinstalled)
... and I had concluded that this is spurious and does not matter.
Does this mean that the various dirrmtrys have to be deleted from pkg-plist? And if yes, which ones? - I generated this quite a while ago when I initially created the port for me using some automatic FreeBSD tool from the porter's handbook, so I thought they are correct.
with redports, sometimes issues in dependencies can cause leftovers I think. If we still see leftovers in poudriere then it's a legitimate error.
If your port created this directory then it needs to try to remove it, however. The question is: What port created it?
Created attachment 145833 [details]
shar: new pkg-plist without @dirrmtry
I have now deleted all @dirrmtry entries because a) the latest 'make makeplist' does not generate them any more and b) it seems the directories actually belong to the standard /usr/local mtree.
The 'leftover' is gone: https://redports.org/buildarchive/20140815192000-41322/
Next committer, note this depends on bug 188854 so consider taking that if it's still open.
Lichray was correct:
That's not going to work, all new ports must come with maintainers, usually it is the person that opened the PR.
Are you going to be the maintainer, Martin?
O.k. I'll maintain it. Do you need another patch, or will you change the maintainer yourself?
Another question to lichray@: fprintd is not particularly intelligent. Do you have a better authentication application? One that preferably also deduces the user name from the fingerprint, and also still allows to use the standard password dialog as an alternative? (Under Windows, my FP reader is always on whenever authentication is required, and it deduces the username by itself.)
lichray is not in CC so he didn't get the question.
You don't have to submit a new shar, hopefully we'll remember to set you as maintainer.
A commit references this bug:
Date: Sun Aug 24 17:24:04 UTC 2014
New revision: 365978
Fprintd is a D-Bus daemon that offers libfprint functionality over
the D-Bus interprocess communication bus. By adding this daemon
layer above libfprint, we solve various problems related to multiple
applications simulatenously competing for fingerprint readers.
While it is not very nice to think of a daemon being necessary in
this scenario, fprintd will be launched by D-Bus through the
activation mechanism. This means it is launched only when needed,
and additionally it will shut itself down after a period of inactivity.
(Text copied from link below.)
Submitted by: Martin Birgmeier
Committed. Good work on this port!