concerning libgpg-error

Werner Koch wk at
Thu May 13 12:12:47 CEST 2004

On Thu, 13 May 2004 11:33:11 +0300, Nikos Mavroyanopoulos said:

> minimum part of it that is required for it to work. Only the .h file should
> be updated if new error values are used in libgcrypt. If this is not possible

and that is excaly what makes maintenance hard.

> a disable option to disable completely error printing (and thus the
> dependency to libgpg-error) would also help.

Disabling error printing is a Bad Thing.  You will get weird bug
reports taking a long time to duplcate them and finally it is a simple
thing which could have been figured out by the error message directly.
After all we went for this shared libary with markers for the
subsystem to make bug tracking easier.  By not having a central place
to maintain this information (the shared library) this effort would be
rendered mostly fruitless.

What is the real problem you have with libgpg-error?  Does it not
build cleanly on all systems?  I'd like to hear about such things




More information about the Gcrypt-devel mailing list