Alon Bar-Lev wrote:
On 2/8/07, Wolfgang Glas <[EMAIL PROTECTED]> wrote:
Does anybody have a better idea, any arguments against this procedure?
Well... I have my own copy at pkcs11-helper...
But I think it is best to have a simple "stupid" package and
dependency for all projects, so that this file will be usable by all
the open source community as a standalone package which installs it at
include directory.
that would be extra work for both the distributions and everyone who
wants to compile software himself. lets face it: out of date pkcs11.h
file is a developer problem, and it is one we can face easily and handle
easily. also we notice quite fast: only if our software doesn't compile
there is a problem - since pkcs#11.h is a ABI standard it only grows but
doesn't change or shrink.
so the real world risk of outdated pkcs11.h files and trouble with it
isn't that big, and it can be managed.
lets not put extra work on other peoples shoulders - compiling is
already a pain, please keep it simple. we can manage those few extra
copies of pkcs11.h files.
Andreas
_______________________________________________
opensc-devel mailing list
opensc-devel@lists.opensc-project.org
http://www.opensc-project.org/mailman/listinfo/opensc-devel
