[Debian-med-packaging] Bug#856984: fis-gtm: please enable openssl support

[Sebastian Andrzej Siewior]

On 2017-12-13 08:33:02 [+0100], Andreas Tille wrote:
> Hi Sebastian,
Hi Andreas,

> it would be nice if you could answer the question below.  Otherwise
> we would set the bug to wontfix for the moment.

somehow this email never reached me or I skipped it by accident.

> Thank you
> 
>         Andreas.
> 
> On Wed, Mar 29, 2017 at 08:50:57PM +0000, Shah, Amul wrote:
> > If I understood your question correctly, you are asking for the fis-gtm package to either enable openssl OR drop the libssl-dev requirement.
> > 
> > We dropped the openssl using encryption plugin libraries from the distributed package because of the "openssl advertising clause". To work around the advertising clause, we distribute our encryption plugin libraries as source, letting the end users that desire encryption support compile it for themselves. So we can't enable openssl.
> > 
> > The fis-gtm package builds the encryption plugin sources as a compatibility test build. That compatibility test build alerted us to the upcoming changes in openssl 1.1. So we won't drop the libssl-dev requirement.
> > 
> > If the above makes sense, I would like to close this bug. If you have some other option, let me know.

That makes sense. I wanted to ensure that you don't depend on it for no
reason or that openssl support is disabled because the new openssl is
not properly detected (we had both cases it the past). If I remember
correctly, then I could not find a difference to build and without
libssl-dev and the changelog said that encryption was temporary disabled
(or something like that).

If you are saying that as part of the build process you do use openssl
and that the build would fail if the openssl library would have changed/
became incompatible for the source you distribute then this is fine.

> > 
> > Thanks,
> > Amul

Sebastian