4 ms·
How is this “inclusion” typically done for a project that is deployed in compiled format and contains hundreds of libraries with dozens of different licenses? I
by alkonaut 6y ago
How is this “inclusion” typically done for a project that is deployed in compiled format and contains hundreds of libraries with dozens of different licenses? It must be especially difficult on devices where it’s difficult to accept user input or display licenses.
In commercial desktop software I have shipped, it has been a section in help>about with a long list of third party libs each showing a text document.
- CameronNemo 6y agoI downloaded trivy (a go CLI tool) recently and they have some tooling to pack up dependency licenses and include them in the release tarball. It is possible and quite easy, if you plan ahead. Notably, Debian binary packages include extensive copyright information.
- alkonaut 6y agoBut are licenses only included in e.g a zip with binaries but not available from “within” the software counting as included/available? For anything distributed as source it’s easy enough.