Re: [opensc-commits] svn pam_pkcs11 changed [135] pam_pkcs11.so to be installed under /lib/security instead of /usr/lib/security

[Andreas Jellinghaus-2]

On Thursday 01 September 2005 13:13, [hidden email] wrote:
> Revision: 135
> Author:   jonsito
> Date:     2005-09-01 11:13:38 +0000 (Thu, 01 Sep 2005)
>
> Log Message:
> -----------
> pam_pkcs11.so to be installed under /lib/security instead
of /usr/lib/security

...

> +libdir = ${prefix}/../lib/security
> +

that does not work with "make distcheck".

my suggestion is: simply use @libdir@/security
and suggest the people to use
        ./configure --prefix=/usr --libdir=/lib

also note: with the default prefix /usr/local/
your version would create /usr/security, right?
you don't want that. (or did you change prefix
default to /usr?)

still, it does not make sence to me to install
pam modules in /lib/security if their libs
are in /usr/lib/. so people could as well
install pam modules in /usr/lib/security/
and than add symlinks, if pam fails to load
the modules from that directory.

anyway, I'd recommend to not use "../" anywhere
in the default config nor install anything
outside $prefix. both breaks make distcheck.
better to instruct the users how to configure
it and hope they do that right, or add
symlinks later.

Regards, Andreas
_______________________________________________
opensc-devel mailing list
[hidden email]
http://www.opensc.org/cgi-bin/mailman/listinfo/opensc-devel

[Jonsy (teleline)]

El jue, 01-09-2005 a las 20:34 +0200, Andreas Jellinghaus escribió:
[...]
> > +libdir = ${prefix}/../lib/security
> > +
> that does not work with "make distcheck".

Extrange... worked fine in my Fedora Core 4
(I use resulting tgz file to make a "rpmbuild -ta xxxx.tgz" )

Anyway, reverted. The only problem is that PAM looks for their
modules at /lib/security by default, so we'll need write full
pathname at /etc/pam.d/xxxx entries, or use symbolic links

About your other mails:

Perhaps, after all you're right and the GNU documentation
must be burned in hell.... :-). Evidently, pam_pkcs11 must
follow OpenSC team conventions. I'll update Makefiles.am
to "proper" handling of "make maintainer-clean"

And finally: Expected to release pam_pkcs11-0.5.3 next
week. 0.5.3 will be the last "independent" version, as
we'll start with lib_p11 integration for 0.6

Juan Antonio

PS:
Sorry: I've stolen some code of your pam_p11 modules... :-)

_______________________________________________
opensc-devel mailing list
[hidden email]
http://www.opensc.org/cgi-bin/mailman/listinfo/opensc-devel

[Andreas Jellinghaus-2]

On Thursday 01 September 2005 22:17, juan antonio martinez wrote:
> Perhaps, after all you're right and the GNU documentation
> must be burned in hell.... :-). Evidently, pam_pkcs11 must
> follow OpenSC team conventions. I'll update Makefiles.am
> to "proper" handling of "make maintainer-clean"

feel free to use different convetions. but at least for me
it would be more work. but I'm only doing very little work
here, so it is more important what works well for your
and ludovic.

> And finally: Expected to release pam_pkcs11-0.5.3 next
> week. 0.5.3 will be the last "independent" version, as
> we'll start with lib_p11 integration for 0.6

good!

> Sorry: I've stolen some code of your pam_p11 modules... :-)

fine with me :)

Andreas
_______________________________________________
opensc-devel mailing list
[hidden email]
http://www.opensc.org/cgi-bin/mailman/listinfo/opensc-devel