0.15.1 Draconian autoconf behavior

[Andreas Metzler]

Hello,

0.5.1 has a rather unfriendly autoconf behavior:

* Hard failure if libtasn1 cannot be located by pkg-config unless
  --without-libtasn1 is set
* Hard failure if libtasn1 cannot be located by pkg-config unless
  --disable-trust-module is set on top of --without-libtasn1.

Is it intended behavior that setting two autoconf options is required for
building p11-kit without libtasn1?

I could try to provide a patch which is a litle bit more friendly. -
No hard failure unless the user has requested something on the
commandline that cannot be done: E.g. hard-failure if
--enable-trust-module is set explicitely but libtasn1 is not
available. But OTOH if the user has not set --enable-trust-module or
--disable-trust-module simply check for tasn1 and if it is not
available bulild without, instead throwing an error.

What do you think about this?

cu Andreas
-- 
`What a good friend you are to him, Dr. Maturin. His other friends are
so grateful to you.'
`I sew his ears on from time to time, sure'