Closed haysam closed 1 year ago
bitpit is not redistributing (nor installing) any of these libraries.
Also, what if someone downloads bitpit and links it against OpenBLAS, or ATLAS or MKL? Should we include the licenses of all possible BLAS implementations? The same applies to MPI (which seems missing from the list) and to METIS (one can use SCOTCH instead of METIS).
I mean, we can include the file if it is needed by the GDPR, I'm just wondering how we can include the licenses of all possible third party libraries bitpit can be linked against (bitpit needs the glibc library, should we include also the license of that library?).
bitpit is not redistributing (nor installing) any of these libraries.
Also, what if someone downloads bitpit and links it against OpenBLAS, or ATLAS or MKL? Should we include the licenses of all possible BLAS implementations? The same applies to MPI (which seems missing from the list) and to METIS (one can use SCOTCH instead of METIS).
I mean, we can include the file if it is needed by the GDPR, I'm just wondering how we can include the licenses of all possible third party libraries bitpit can be linked against (bitpit needs the glibc library, should we include also the license of that library?).
I agree. If we don't redistribute libraries with bitpit we don't need third parties licenses. We could update the required dependencies in INSTALL.md if needed (for instance, boost and rapidjson [both optionals] seem missing).
THIRPARTIES.md contains a lot of third party components and their licenses to scope with inherited license obligations