I accidently installed both at the same time, and only later discovered that this is not necessary and even to be avoided. See the developer's manual here: http://www.n-view.net/Appliance/fingerprint/doc/Step-by-step-manual.html "The following applications are known to conflict with Fingerprint GUI: thinkfinger, pam-fprint, pam-fprintd..." Therefore, sys-auth/pam_fprint and fprintd (should it be added to portage) should be added as a blocker to fingerprint-gui. sys-auth/thinkfinger already is.
(In reply to haarp from comment #0) > I accidently installed both at the same time, and only later discovered that > this is not necessary and even to be avoided. See the developer's manual > here: > > http://www.n-view.net/Appliance/fingerprint/doc/Step-by-step-manual.html > "The following applications are known to conflict with Fingerprint GUI: > thinkfinger, pam-fprint, pam-fprintd..." > > Therefore, sys-auth/pam_fprint and fprintd (should it be added to portage) sys-auth/fprintd is in portage. > should be added as a blocker to fingerprint-gui. sys-auth/thinkfinger > already is. These are different applications/approaches to archive similar goals. Only one should be configured in pam and the corresponding scan programs have to be used, agreed. But they can be installed/present at the same time, no filename conflicts and no interference, I'm aware of. Please reopen if you can prove me wrong here, thanks.
