Hi,

I am planning to package a small bit of code that is MIT licensed and is intended to be used via LD_PRELOAD to overload and inflience the bind()
syscall regarding source address selection.

Is the MIT License sufficiently compatible to the (L)GPL to allow this
use? The code interfaces both with the (arbitrary) application issueing
the bind() call and the glibc. Is that a linking issue?

Greetings
Marc

-- ----------------------------------------------------------------------------- Marc Haber | "I don't trust Computers. They | Mailadresse im Header Leimen, Germany | lose things." Winona Ryder | Fon: *49 6224 1600402 Nordisch by Nature | How to make an American Quilt | Fax: *49 6224 1600421

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

"Marc" == Marc Haber <mh+debian-legal@zugschlus.de> writes:

Marc> Is the MIT License sufficiently compatible to the (L)GPL to
Marc> allow this use? The code interfaces both with the (arbitrary)
Marc> application issueing the bind() call and the glibc. Is that a
Marc> linking issue?

I believe MIT should be fine for this.

I'm sure there is some corner case with some application somewhere where
this is problematic because there always is.
But fram a practical standpoint, I think what you are proposing should
be fine.

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

On Mon, 21 Jun 2021 10:10:57 +0200 Marc Haber wrote:

[...]

Is the MIT License sufficiently compatible to the (L)GPL to allow this
use?

I assume that, by MIT, you mean the [Expat] license.

[Expat]: <http://www.jclark.com/xml/copying.txt>

As far as I can tell, the [Expat] license is basically compatible with
(almost) anything... Hence, unless I am really mistaken, I would say
that there should not be any showstopper.


--
http://www.inventati.org/frx/
There's not a second to spare! To the laboratory! ..................................................... Francesco Poli .
GnuPG key fpr == CA01 1147 9CD2 EFDF FB82 3925 3E1C 27E1 1F69 BFFE

-----BEGIN PGP SIGNATURE-----

iQIzBAEBCgAdFiEEygERR5zS79/7gjklPhwn4R9pv/4FAmDQuQoACgkQPhwn4R9p v/71RA/+KsyM5TisbNWGz8XepyWfIvuBjZMZ54J0vsfMxZmxp6lC9ypJLW2q/uV5 dgDgf5ofjKh4dnzJykF2pv7BSIz6WT82gToS8eSqoQcbGZT6am99Nz+p2hHZgElh Qd6VHca+yS8D6JCGReVf9bSc309ev+9+KbhU/Tn1S/i6fCGy3GlM/UCYX5JWa2td HNxBfRZApmZ2QAdY0qYDcZeWa6cPEczrg1cPG141X3m6aE9Y2RNTixYp00vzcqFN DP5dOYIA+RDZBkNrLMOJKCDaCv7NtywXtRo4hC4Vk76ZIS2smkD7NsConG6b3hvN gNrre8PxdC1CCwr1udyYXRPp1VDPuJCqBTYHWsXwVmpukRbGG4y30w1a6lfEZPhc fA4tSUSt2JjUjyFBJaZtXCe0UYPkGbPOfVnZQZwyuJpivWVYlbtSJcjI6j8I22K6 rPV2b4dey8UpKeyOqfL8trSzGLuaoyyO9jzUltClDiyKDbdXPm9f01Tqr+BeBcBE iciWlznhzZWw3Horb0VGZktbtGp5s4G+/VvsjefiMUaPOSRFV2Ihb0A3MjtKBPNs HG+LSKdISccJewbIkGPWwzQWm3XPeQsY6gH4tpzlF4QrFL0kC2TTiahE0bHpHMQI XGmx3+uquUNoVc49EmlwDUKQDOMsSLv7

Marc Haber <mh+debian-legal@zugschlus.de> writes:

I am planning to package a small bit of code that is MIT licensed and is intended to be used via LD_PRELOAD to overload and inflience the bind() syscall regarding source address selection.

Is the MIT License sufficiently compatible to the (L)GPL to allow this
use? The code interfaces both with the (arbitrary) application issueing
the bind() call and the glibc. Is that a linking issue?

As far as I understand, the LGPL does not limit the use of a program.

And when you create or distribute a package, you are only bound to the
license conditions of the code pieces that you use to create it. As
long as your binary package is not a derivative of an (L)GPL program,
its license conditions cannot be influenced by (L)GPL.

Best

Ole

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)