GPGME 0.4.1 -- compile hassles

[Bernhard Reiter]

--mP3DRpeJDSE+ciuQ
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Tue, Jul 22, 2003 at 03:53:20PM +0200, Marcus Brinkmann wrote:
> On Tue, Jul 22, 2003 at 03:29:35PM +0200, Bernhard Reiter wrote:
> > Thanks for the answer.
> > Note: I probably won't be able to test CVS in the near future.
>=20
> Is that a problem of getting at the changes in CVS or something different=
?=20
> If it is the former, I could email you the patches.

Just the normal timeconstraints on my part...

> > Wouldn't that we a good idea to check for the minium version
> > number for gpg and gpgsm and issue a warning in the configuration step?
>=20
> Well, yeah, it could do that.  But it can only be a warning because the
> machine you compile GPGME on doesn't even need to have gpg or gpgsm
> installed (unless you want to run the test suite).  But as I have to check
> for running the test suite anyway, I can add a check.  The check would
> disable the test suite if no suitable gpg is found.

A warning, but a big one, should be fine.=20

--mP3DRpeJDSE+ciuQ
Content-Type: application/pgp-signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.1 (GNU/Linux)

iD8DBQA/HVxgh9ag3dpKERYRAny/AJ9+UzlE37O0p3BOHcV1bitK1ZqTVwCfaoU2
awVjGaflDlHuBU2LTaR4t44=
=DYnU
-----END PGP SIGNATURE-----

--mP3DRpeJDSE+ciuQ--