Hello, On Mar 21, 2011, at 19:30 , Viktor TARASOV wrote: > Le 21/03/2011 18:09, Martin Paljak a écrit : >> On Mar 12, 2011, at 4:20 PM, webmas...@opensc-project.org wrote: >>> Revision: 5226 >>> Author: vtarasov >>> Date: 2011-03-12 14:20:13 +0000 (Sat, 12 Mar 2011) >>> >>> Log Message: >>> ----------- >>> msi: include 'cardmod.dll' and 'rutoken' PKCS#15 profiles into MSI >> For easily repeatable builds and for the sake of simple nightly builds [1], >> I'll do the following changes to the windows makefile based building unless >> there are objections: > Have no objections, thank you .
After some fighting with WinSCP, the setup is now done (meaning it builds and uploads as necessary) and sample MSI builds have been uploaded to the nightly directories [1], both for x86 and x64. Windows7 build machine is currently offline but will be brought back online for next week and onwards (have a look at how upgrading to Windows SP1 went: http://martinpaljak.net/windowswtf.png ) The version number in the installer file name consists of SVN_REVISION.BUILD_NUMBER where the BUILD_NUMBER differs when the build machinery has been changed or a manual build requested. It is sequential and managed by Jenkins. Probably .deb packages for Ubuntu 10.10 and Debian testing will also be added to the nightly binary packaging machine in near future, based on samples in ticket #216. Some comments about the MSI that need to be dealt with before release, IMHO: * License in installer: CPL -> LGPLv2. Maybe some nice theming for the installer, a la OS X background. * Components panel either removed or fixed (currently there seems to be "something" but there are empty strings for the main and subcomponent) * Installation location. The distributed DLL-s should IMO go to Windows folder. The three files that should go to system32 or equivalent are: * opensc.dll - does not pollute nor should it conflict with other software. * opensc-pkcs11.dll - predictable/known path for the PKCS#11 module. * opensc-cardmod.dll - most other minidrivers install to system32 as well. * none of them is a "program file" but relate to system services to some extent. Also I don't know any practical reasons why it should be in the installation folder in program files, other than "it would be nice" and "it may contribute to dll hell" (compare to GUID vs other unique id formatting) * Directory layout. Windows is not Unix. The directory layout is hand picked by the wix script anyway, so I'd suggest something following in C:\Program Files\OpenSC \opensc.conf \tools\opensc-explorer.exe \tools\... \profiles\oberthur.profile \profiles\... * Start menu entries, if any. I'd suggest "OpenSC tools folder" and a link to opensc-project.org documentation. Or only a link to the documentation. * File versioning. Current .rc uses the libtool related version in the file versioning which is not optimal. It has to my knowledge no relation to the libtool interface versioning. Versions from OpenSC version and SVN revision could be used instead. 0.12.1.5247 for r5427 in the 0.12.1 build cycle * Testing for conditional installability based on architecture and OS release (will matter for minidriver installs, XP with minidriver 5 is not OK for some operations and multiple PINs.) Future releases would be picked from the nightly builds, the file name changed (svn and build versions removed), checksummed, signed and frozen. So nightlies could be (and should be) tested as pre-releases all the time. Some generic installer issues affect the OS X installers as well (like proper documentation in installer panes) but other than that I hope to get everything ready during next week for a 0.12.1 release. The release after that will happen based on a pre-set timer (meaning when the date arrives, not "it is ready when it is ready", maybe T+2 or T+3 weeks. So please be ready for several build/install related changes early next week and if possible, test a lot. Have a nice and sunny weekend, Martin [1] http://www.opensc-project.org/downloads/nightly/ _______________________________________________ opensc-devel mailing list opensc-devel@lists.opensc-project.org http://www.opensc-project.org/mailman/listinfo/opensc-devel
