Relicensing the rocm-llvm debian directory
Hello ROCm Team,
If we wish to package the full rocm-llvm fork, it would be useful to
share code between the debian directories of llvm-toolchain and
rocm-llvm. AMD intends to package the full rocm-llvm fork as an option
on Ubuntu, but it's up to the community to decide if that is desired in
Debian. I'm ambivalent on the matter, but I think it would make sense to
at least prepare so that it could be easily adopted if there is user
demand for it.
One aspect of sharing code that will be quite tedious to handle is the
licensing. The debian/* directory of llvm-toolchain is licensed Apache
2.0 with LLVM Exceptions [1], whereas the debian/* directory of
rocm-llvm is licensed Expat [2]. When mixing the two, we will have to
track which files are under which license.
If we license new contributions to rocm-llvm as Apache 2.0 with LLVM
exceptions, that would help to reduce d/copyright updates for the debian
directory when we pull in changes from the llvm-toolchain package. I
would also ask the existing copyright holders for the rocm-llvm debian
directory if they would be willing to reliscence their contributions as
Apache 2.0 with LLVM exceptions.
Sincerely,
Cory Bloor
[1]:
https://salsa.debian.org/pkg-llvm-team/llvm-toolchain/-/blob/20/debian/copyright?ref_type=heads#L28-30
[2]:
https://salsa.debian.org/rocm-team/rocm-llvm/-/blob/debian/6.4.3+dfsg-1_exp3/debian/copyright?ref_type=tags#L83-86
Reply to: