[Csync2] csync2 without gnutls-openssl?

Lars Ellenberg lars.ellenberg at linbit.com
Wed Jul 28 14:48:44 CEST 2010


On Wed, Jul 28, 2010 at 02:35:41PM +0200, Giampaolo Tomassoni wrote:
> > That is probably due to gnutls having changed to pkg-config.
> > Please rather patch configure.ac to use pkg-config than
> > go back to m4.
> 
> Lars, AM_PATH_LIBGNUTLS was completely undefined, so the
> pkg-config/gnutls-config isn't that much relevant with respect to the
> autogen.sh failure.

Yes, it is undefined, because it should be (or used to be) in the dev
package of libgnutls, but no longer is, because they apparently decided
they had a better approach.

> In the patch shipped with my previous message, the m4/libgnutls.m4 file was
> exactly meant to define the missing macro.

Yes.
And your patch even fixes a build breakage.
So it is good.
Only it seems to be not what libgnutls upstream seems to want.
So I figured, if you already hacking there anyways, maybe just do it the
way gnutls upstream feels would be the right way.

> Do you perhaps mean you prefer to have the AM_PATH_LIBGNUTLS AC_DEFUN[]
> stuff directly into configure.ac, instead of having it in the
> m4/libgnutls.m4 file?

I don't care either way. But if gnutls still things this macro should be
how autofoo should be done, then they should package it themselves,
just as it used to be. Or we should do whatever they feel is the right
way to gnutls autofoo integration now.

It cannot possibly be their intention that any libgnutls user should
have its own private copy of libgnutls.m4.

Am I misunderstanding something?

Is this just a packaging error of libgnutls?

-- 
: Lars Ellenberg
: LINBIT | Your Way to High Availability
: DRBD/HA support and consulting http://www.linbit.com

DRBD® and LINBIT® are registered trademarks of LINBIT, Austria.


More information about the Csync2 mailing list