Le samedi 17 mars 2012 à 22:15 +0100, Viktor Tarasov a écrit : > Excellent, I will prepare the guidelines for the procedure. > Thanks.
Perfect. During the week-end, I installed a fresh Super-micro server at the office. It is running a Debian x64 with encrypted file system on a 60G solid state drive. The hardware is running with an IPMI card providing cold/hot reset, serial over IP and monitoring to ensure the server is always up and running. It is running on electrical backup for 24x24 operation. So we stand ready to provide the first packages whenever needed. > You should not be disappointed - the naming policy is open for > suggestions. > The current one is just the rapid 'working' solution. This is a translation problem, sorry. I am not "disappointed". :) About naming, I would suggest to mimic VLC lightlies, at this URL: http://nightlies.videolan.org/build/win32/?C=M;O=D For Windows: opensc-$version-$branch-$yyyymmdd-$hhmm-$platform-$debug.$suffix For Mac OSX: opensc-$version-$branch-$yyyymmdd-$hhmm-$platform.$suffix Where: branch = "staging" or "sm" if we have two branches, or simply "git" if there is only one branch. version = 0.12.3 (major-minor). yyyymmdd = 20120319 (19 March 2012) hhmm = 0112 (one hour 12 minutes) platform = x32 or x64 debug = "debug" or none. suffix = 7z, zip, exe or msi So we can have as many compilations as needed during the day. To comply with Debian rules: We may have to add a leading "O-" to the Debian versions. And set priority to zero. We have to think about a simple way to accommodate with several GIT versions. Maybe it could be a virtual apache host, i.e. gitversion.domain.org. So we can provide different APT repositories. Kind regards, -- Jean-Michel Pouré - Gooze - http://www.gooze.eu
smime.p7s
Description: S/MIME cryptographic signature
_______________________________________________ opensc-devel mailing list opensc-devel@lists.opensc-project.org http://www.opensc-project.org/mailman/listinfo/opensc-devel
