Release 0.12

_______________________________________________
opensc-devel mailing list
opensc-devel@...
http://www.opensc-project.org/mailman/listinfo/opensc-devel

Am Freitag 23 Oktober 2009 11:49:20 schrieb François Leblanc:
> Does release 0.12 will have all this libraries or put in only one
> libopensc?

IIRC the current plan is:

opensc will still have "opensc-pkcs11.so" as we used to,
and also "libopensc.so" but for internal use only
(used by pkcs15-init etc. but not a recommended interface for
3rd party applications).

libscconf and libpkcs15init will be merged with libopensc.

Andreas
_______________________________________________
opensc-devel mailing list
opensc-devel@...
http://www.opensc-project.org/mailman/listinfo/opensc-devel

Yes.
I can work on this.
Is everything else finished and merged?
svn is difficult in merging back after file move.

2009/10/23 Andreas Jellinghaus <aj@...> _______________________________________________
opensc-devel mailing list
opensc-devel@...
http://www.opensc-project.org/mailman/listinfo/opensc-devel

Am Freitag 23 Oktober 2009 17:49:57 schrieb Alon Bar-Lev:
> Yes.
> I can work on this.
> Is everything else finished and merged?
> svn is difficult in merging back after file move.

lets wait till we merged 0.12 and trunk.
I guess martin knows best how to handle that,
maybe he has a git svn, so he can merge his changes
as series, but a merge as a single large diff would
be ok too. (or the rm/mv combo as worst case.)

for the library changes: I know what should be needed to do:
move libopensc definition (for the shared lib) from src/libopensc/
to src/, and convert the libs in src/libopensc/ lib/pkcs15init/ and
lib/scconf/ to noinst_ libs (see src/common/ it has already "libcommon.la"
which is later included as .a archive in linking, and libtool/automake
handle everything correctly.

so implementation should be easy.

Regards, Andreas
_______________________________________________
opensc-devel mailing list
opensc-devel@...
http://www.opensc-project.org/mailman/listinfo/opensc-devel

On 24.10.2009, at 9:35, Andreas Jellinghaus wrote:
> Am Freitag 23 Oktober 2009 17:49:57 schrieb Alon Bar-Lev:
>> Yes.
>> I can work on this.
Great!

>> Is everything else finished and merged?
>> svn is difficult in merging back after file move.
>
> lets wait till we merged 0.12 and trunk.
> I guess martin knows best how to handle that,
> maybe he has a git svn, so he can merge his changes
> as series, but a merge as a single large diff would
> be ok too. (or the rm/mv combo as worst case.)
I think that one big merge commit from branch is the best solution at  
the moment.



> for the library changes: I know what should be needed to do:
> move libopensc definition (for the shared lib) from src/libopensc/
> to src/, and convert the libs in src/libopensc/ lib/pkcs15init/ and
> lib/scconf/ to noinst_ libs (see src/common/ it has already  
> "libcommon.la"
> which is later included as .a archive in linking, and libtool/automake
> handle everything correctly.
There are some other things as well:
1. Signer - either drop it or extract it (if there are users who claim  
it on the mailing list) I still claim that it is not of interest to  
most users. And that it has very few if any users in real life.
2. p15emu-westcos.c. Problem: consistent naming. Rest of the emulation  
drivers use pkcs15-<name>.c As there are pkcs15-foo.c files in src/
libopensc that deal with other tasks than emulation, maybe push the  
emulation drivers into a subdirectory for clarity?

--
Martin Paljak
http://martin.paljak.pri.ee
+372.515.6495




_______________________________________________
opensc-devel mailing list
opensc-devel@...
http://www.opensc-project.org/mailman/listinfo/opensc-devel

Am Samstag 24 Oktober 2009 10:45:42 schrieb Martin Paljak:
> I think that one big merge commit from branch is the best solution at
> the moment.

ok, fine with me.

> There are some other things as well:
> 1. Signer - either drop it or extract it (if there are users who claim
> it on the mailing list) I still claim that it is not of interest to
> most users. And that it has very few if any users in real life.

drop it. maybe I can create a new project and create a release, but I
doubt there is much use for it. never used it myself.

> 2. p15emu-westcos.c. Problem: consistent naming. Rest of the emulation
> drivers use pkcs15-<name>.c As there are pkcs15-foo.c files in src/
> libopensc that deal with other tasks than emulation, maybe push the
> emulation drivers into a subdirectory for clarity?

I'm fine with renames. a subdirectory below src/ ?
(i.e. not src/libopensc/pkcs15emu).

also I would be fine with merging directories, or other bigger strutural
changes. now is a good time to discuss what changes we can do and if
those will help us to structure the code better, make it easier to understand
and maintainer it easier.

Regards, Andreas
_______________________________________________
opensc-devel mailing list
opensc-devel@...
http://www.opensc-project.org/mailman/listinfo/opensc-devel

Hi,


Warning, there are pkcs15-westcos.c in pkcs15init dir so if you change the name you will have a problem merging pkcs15init into libopensc (is the reason why I've kept p15emu-westcos instead of pkcs15-westcos).

More other pkcs15-xxxx in libopensc concern emulated cards, so  I suggest to rename all pkcs15-xxxx.c in libopensc by p15emu-xxxx.c and change pkcs15-foo.c name (if it deal other than emulation).

(I use both since I have small westcos 2ko without pkcs15 structure inside and bigger one where I can put pkcs15 structure... Perhaps other cards can have the same so it will be great to keep it possible and have a convention naming that let us do it...)

Regards,

François.
_______________________________________________
opensc-devel mailing list
opensc-devel@...
http://www.opensc-project.org/mailman/listinfo/opensc-devel