[Debian-med-packaging] Bug#856984: fis-gtm: please enable openssl support
Shah, Amul
Amul.Shah at fisglobal.com
Thu Dec 14 08:35:08 UTC 2017
Hi Sebastian,
From: Sebastian Andrzej Siewior [mailto:sebastian at breakpoint.cc] Sent: Thursday, December 14, 2017 9:08 AM
On 2017-12-13 08:33:02 [+0100], Andreas Tille wrote:
>> On Wed, Mar 29, 2017 at 08:50:57PM +0000, Shah, Amul wrote:
> somehow this email never reached me or I skipped it by accident.
[amul] I blame the Outlook formatting! It would make anyone not want to read email! ;)
>> > 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).
[amul] Understood and I agree with your stance. There is no need for
dependencies that get in the way of moving forward.
>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.
[amul] That is what I am saying. Can we close this bug?
Thanks - Amul
The information contained in this message is proprietary and/or confidential. If you are not the intended recipient, please: (i) delete the message and all copies; (ii) do not disclose, distribute or use the message in any manner; and (iii) notify the sender immediately. In addition, please be aware that any message addressed to our domain is subject to archiving and review by persons other than the intended recipient. Thank you.
More information about the Debian-med-packaging
mailing list