Therefore, if someone builds on top of my system with proprietary integrations I don't see any way they can fulfill the promises of the LGPL license. Rust instead seems to statically link these libraries into the final assembly, which makes them irreplaceable. In C++ and C# this is no big deal, as I can dynamically link to these libraries and the separation is obvious, making it easy to adhere to the LGPL license. The rust libraries that create the rust abstractions are MIT licensed so I'm good from that aspect, but the libraries themselves are LGPL at a minimum (more on that in a bit). Now I need to add in-process transcoding capabilities, which requires either embedding gstreamer or ffmpeg. Right now this is fine because some advanced functionality utilizes shelling out to an ffmpeg executable, and it's up to the user to download and pick what they want to use (it can be used without the advanced functionality and thus ffmpeg isn't a hard requirement). I licensed it as MIT specifically because if some users want to customize it and add proprietary integrations they can do so without being forced to open-source their integrations. I've worked a lot on a media workflow server with the intention that it can be used by both open source and non-open source projects ( ).
0 kommentar(er)
