From: Arnout Vandecappelle <arnout@mind.be>
To: David Laight <David.Laight@ACULAB.COM>,
"Yann E. MORIN" <yann.morin.1998@free.fr>,
Fabrice Fontaine <fontaine.fabrice@gmail.com>
Cc: Bernd Kuhls <bernd.kuhls@t-online.de>,
"buildroot@buildroot.org" <buildroot@buildroot.org>
Subject: Re: [Buildroot] [PATCH 1/1] package/fetchmail: fix build with libressl
Date: Mon, 4 Apr 2022 17:12:14 +0200 [thread overview]
Message-ID: <13ee969c-e0cd-7029-5853-cc3cbd5baa06@mind.be> (raw)
In-Reply-To: <5771e60200854118a380e4b47b540f68@AcuMS.aculab.com>
On 04/04/2022 10:41, David Laight wrote:
> From: Arnout Vandecappelle
>> Sent: 04 April 2022 08:35
>>
>> On 03/04/2022 22:15, Yann E. MORIN wrote:
>>> Fabrice, All,
>>>
>>> On 2022-04-03 20:53 +0200, Fabrice Fontaine spake thusly:
>>>> Fix the following build failure with libressl raised since bump to
>>>> version 6.4.29 in commit ba6fd52195f2e3d0b04baae40cfe084226824d31 and
>>>> https://gitlab.com/fetchmail/fetchmail/-/commit/340d00bf9910ed55163be26435f70baf65a64f9d:
>>>>
>>>> configure: error: fetchmail cannot legally be linked against LibreSSL for lack of GPL2 clause 2b
>> exception. See COPYING.
>>>
>>> This sentence is incorrect. It is legally not possible to *distribute*
>>> fetchmail when linked against LibreSSL, as the GPL conditions in that
>>> case only trigger at the moment of distribution.
>>>
>>> So, there should be no issue with linking fetchmail to LibreSSL for
>>> private use without redistribution.
>>
>> It would be nice though if this could be mentioned in legal-info.
>
> ISTM that the default needs to be to disable the build.
> Requiring 'hoops be gone through' for a private build.
The "hoop" is to use openssl rather than libressl. Doesn't sound too complicated.
Regards,
Arnout
>
> David
>
> -
> Registered Address Lakeside, Bramley Road, Mount Farm, Milton Keynes, MK1 1PT, UK
> Registration No: 1397386 (Wales)
>
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
prev parent reply other threads:[~2022-04-04 15:12 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-03 18:53 [Buildroot] [PATCH 1/1] package/fetchmail: fix build with libressl Fabrice Fontaine
2022-04-03 20:15 ` Yann E. MORIN
2022-04-04 7:34 ` Arnout Vandecappelle
2022-04-04 8:41 ` David Laight
2022-04-04 15:12 ` Arnout Vandecappelle [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=13ee969c-e0cd-7029-5853-cc3cbd5baa06@mind.be \
--to=arnout@mind.be \
--cc=David.Laight@ACULAB.COM \
--cc=bernd.kuhls@t-online.de \
--cc=buildroot@buildroot.org \
--cc=fontaine.fabrice@gmail.com \
--cc=yann.morin.1998@free.fr \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.