Subversion Repository
Engine_pkcs11 is using subversion as version control system. You can find out more about subversion at
- http://subversion.tigris.org/ is the official home for subversion.
- http://svnbook.red-bean.com/ has the book "Version Control with Subversion"
In our subversion repository we have
- trunk/ contains the current development code
- branches/ will contain branches when we need those
- releases/engine_pkcs11-0.x.y contains the engine_pkcs11 0.x.y release code.
You can checkout these with the subversion commands
svn co http://www.opensc-project.org/svn/engine_pkcs11/trunk/ svn co http://www.opensc-project.org/svn/engine_pkcs11/releases/engine_pkcs11-0.1.3/
Note that the subversion repository only contains development files. Before compiling the code you need to run the "./bootstrap" script to create many files like "configure" and "Makefile.in". You need to have autoconf, automake and libtool installed on your system to do that. Also you need (as for normal compiling): pkg-config and openssl (runtime and development).
Some people have reported problems with some http proxies. If you find some problem, you can maybe solve it by using https instead. Try to checkout the repository like this:
svn co --non-interactive https://www.opensc-project.org/svn/engine_pkcs11/trunk/ svn co --non-interactive https://www.opensc-project.org/svn/engine_pkcs11/releases/engine_pkcs11-0.1.3/
Write access for developers
Developers with write access usualy access the repository via https with authentication using ssl client certificates. You might want to put something like this into your ~/.subversion/servers file to point subversion to your client certificate:
[groups] opensc = www.opensc-project.org [opensc] ssl-client-cert-file=/home/aj/.subversion/aj.p12
You can access the repositories:
svn co https://www.opensc-project.org/svn/engine_pkcs11/trunk/ svn co https://www.opensc-project.org/svn/engine_pkcs11/releases/engine_pkcs11-0.1.4/