Mailing List Archive

[PATCH] optional test code building
Gcrypt Dev folks,

Diego protested[1] and blogged[2] not to build examples or tests when
distributors make code. To facilitate this an example[3] was suggested and I
modeled something similar so that disto maintainers can optionally turn off
the building of test code (unless they plan to use it).

Is the attached patch or indead the general concept acceptable?

[1] https://bugs.gentoo.org/show_bug.cgi?id=226287
[2]
http://blog.flameeyes.eu/2008/06/11/please-dont-build-your-examples-by-default
[3]
http://git.flameeyes.eu/?p=others/0pointer/libdaemon.git;a=commitdiff;h=a301690be6581e23a39813444b2904addcb26ab7
--
Daniel Black <dragonheart@gentoo.org>
Gentoo Foundation
Re: [PATCH] optional test code building [ In reply to ]
On Tue, 4 Nov 2008 06:41, dragonheart@gentoo.org said:

> Diego protested[1] and blogged[2] not to build examples or tests when
> distributors make code. To facilitate this an example[3] was suggested and I

I don't think that this is a good idea. This won't allow to run the
selftests. The selftests are there for a reason. If you don't like
that just change it in your system.


Shalom-Salam,

Werner

--
Die Gedanken sind frei. Auschnahme regelt ein Bundeschgesetz.


_______________________________________________
Gcrypt-devel mailing list
Gcrypt-devel@gnupg.org
http://lists.gnupg.org/mailman/listinfo/gcrypt-devel