Doug,
Yes, the proposed change would work.
Thanks,
Brian Thomas
-Original Message-
From: Douglas E. Engert [mailto:deeng...@anl.gov]
Sent: Monday, January 24, 2011 2:11 PM
To: Brian Thomas
Cc: Martin Paljak; opensc-devel@lists.opensc-project.org
Subject: Re: [opensc-devel] Proposed car
On 1/24/2011 12:54 PM, Brian Thomas wrote:
> Hello,
>
> I strongly urge the OpenSC team to make this change to fix mini-driver
> compatibility. Yes, my company "needs this because we just do", however
> by implementing this fix, it will ensure better compatibility with a
> Windows mini-driver an
Hello,
I strongly urge the OpenSC team to make this change to fix mini-driver
compatibility. Yes, my company "needs this because we just do", however
by implementing this fix, it will ensure better compatibility with a
Windows mini-driver and thus a more usable product for more people.
Thanks,
B
Hello,
On Jan 24, 2011, at 3:17 PM, jons...@terra.es wrote:
> > Not that I would want to suggest a "8 meters requirement" [1], something
> > should be done about it.
> [...]
>
> I agree:
>
> In the writting of Spanish DNIe LGPL driver I've found so many times that
> lack of information.
> A s
Hello,
On Jan 24, 2011, at 6:13 PM, Douglas E. Engert wrote:
> I agree with you on this, but there has not been much support for building
> on Windows and it has been hard to find Windows developers and getting Visual
> Studio installed is not easy. Alon and I had this discussion a few years ago
Hello all,
OpenSC 0.12.0 includes scripts to reasonably automatically and repeatably build
the installers on all supported platforms (and of course the standard targzip
for Linux).
The next step, for next release, is to get automated (nightly) builds and
automated tests.
This requires infrastr
On 1/22/2011 8:38 AM, Martin Paljak wrote:
>
> On Jan 14, 2011, at 9:07 PM, Douglas E. Engert wrote:
>> 'On 1/14/2011 12:48 PM, Alon Bar-Lev wrote:
>>> At build script there is a comment:
>>> # Disable until we solve license issue
>>> # if [ -n "${BUILD_FOR_WINDOWS}" ]; then
>>> #
Martin Paljak wrote:
> 2. Use meaningful commit messages,
I find this very very important, *especially* if seeking review from
peers.
> - If it fixes a ticket - include ticket number
Trac can pick up special commands from commit messages and
automatically add references to tickets, or close ti
Hi!
> > One of the longstanding problems of OpenSC is lack of documentation,
> > both developer (source comments, internal architecture, tutorials on
> > how to add new card drivers other way than copypaste etc) and
> > end-user docs. This is unfortunately quite usual for open source
> > projects,
Mensaje original
De: mar...@martinpaljak.net
Fecha: 24/01/2011 12:46
Para: "OpenSC-devel (opensc-devel)"
Asunto: Re: [opensc-devel] [opensc-commits] Fwd: IAS sucks
[...]
> One of the longstanding problems of OpenSC is lack of documentation, both
> developer
> (source comments, interna
Hello,
On Jan 10, 2011, at 6:12 PM, Viktor TARASOV wrote:
> On 10.01.2011 16:01, Viktor TARASOV wrote:
>> From:Andre Zepezauer
>> it's hard to follow all the changes done in the last view days. Here
>> some issues I found so far:
>>
> I do my best, trying to split the changes into the s
11 matches
Mail list logo
