Le Monday 31 May 2004 � 00:24:13, Damien Sauveron a �crit: > Two of theses header files are related to the Muscle library and not to > pcsc-lite and we should move them in the future. Also where do we move them?
We need to split the pcsc-lite-*.tar.gz archive, not necessarily install the Muscle library header files in a different place. Creating a /usr/include/muscle/ directory for just _two_ files is a bit overkill I think. > 2) "pcsc-lite" seems more consistent than "PCSC" as directory name > even if it is not compliant with MacOS X. pcsc-lite is the name of the project. We should avoid using pcsc-lite specific filenames for files common with other PC/SC implementations. All the C libraries have a /usr/include/stdio.h. You don't have /usr/include/gnuc/stdio.h, /usr/include/bsd/stdio.h and /usr/include/solaris/stdio.h. It would be counterproductive. Maybe Microsoft will also use PCSC/ one day but they will never use pcsc-lite/. > We can also put in /usr/[local/]include a symbolic link on winscard.h only for > the backward compatibility purpose with Microsoft and we can add a note that > recommends developers to use the winscard.h located > /usr/[local/]include/pcsc-lite/ or /usr/[local/]include/PCSC/ in their next > developments. Developpers will have to recompile their applications to use libpcsclite.so.1 provided by the next pcsc-lite version 1.3.0. They can also edit the project and add a PCSC/ in the Makefile or the source code. In fact having .h files outside of PCSC/ (or whatever we call it) is not a good idea. It is not clean. > >Any objection to the change? > It is good for me. OK. So we go for /usr/include/PCSC/ :-) Bye, -- Dr. Ludovic Rousseau [EMAIL PROTECTED] -- Normaliser Unix c'est comme pasteuriser le camembert, L.R. -- _______________________________________________ Muscle mailing list [EMAIL PROTECTED] http://lists.drizzle.com/mailman/listinfo/muscle
