On Fri, Mar 14, 2008 at 2:36 PM, Maciek Pasternacki
<maciej(a)pasternacki.net> wrote:
> Hello,
>
> I am not sure if I am writing to correct address. I found your name in
> the LICENSE file of py-configparser library
> (http://common-lisp.net/project/py-configparser/), and got your
> common-lisp.net login name at common-lisp.net recently added projects
> RSS feed.
Well, I *am* the right person, but probably this e-mail address wasn't
really the correct one: I'm usually faster to respond on mails to the
py-configparser-devel mailing list.
> I could not find any other contact info either in
> py-configparser sources, or on the project page.
Hmm. It seems I need to correct that then. Thanks for pointing it out.
> I sent you an e-mail
> on March 6 to ehuels(a)gmail.com address I managed to google out, but with
> no reply. If you are not right person to contact about it, please
> excuse me bothering you and, if you happen to know who would be the
> right person, please direct me to him or her.
>
> I tried to use py-configparser in my project with SBCL on Linux, and I
> had to do some corrections in order for it to compile. DECLAIM forms
> should not be quoted and SBCL refuses to compile parser.lisp; probably
> it had slipped because your Lisp implementation corrects this kind of
> error. Patch that corrects this is attached.
I see that I already corrected this issue. Are you aware of the newer
releases 1.0.2 and 1.0.3?
> I would be grateful if next version of the package followed the
> convention of having at least .asd files at top-level directory after
> unpacking the tar.gz file (now the top-level directory contains only
> 1.0.0 subdirectory).
I hope this issue was fixed in the newer releases too.
> This would make it easier to automatise
> installation of your package with CL-Librarian, which I use to manage
> all other libraries.
Thanks for sending your feedback! I hope you still find the package usefull?
Bye,
Erik.
