rocm-device-libs placement in llvm/clang namespace

[Étienne Mollier]

Greetings LLVM Maintainers,

I am in discussions with ROCm upstream about the placement of
GPU bitcodes libraries [1], and it looks like there is an intent
to move these into llvm namespace in upcoming upstream releases.
Would it be okay that the rocm-device-libs package puts files
somewhere below /usr/lib/TRIPLET/llvm-VERS/ ?

[1]: https://github.com/RadeonOpenCompute/ROCm-Device-Libs/issues/79

Rationale behind that is that bitcodes seem highly dependent on
the llvm version in use, and require tight coupling.  Thinking a
couple of times about it, I believe it is technically okay-ish
(that should work for packages wrapping add-ons of other
packages), but it is also quite possible this would require
coordination when targeting locations not initially thought for
add-ons.

Thanks for your work on packaging llvm!

Have a nice day,  :)
-- 
Étienne Mollier <emollier at emlwks999.eu>
Fingerprint:  8f91 b227 c7d6 f2b1 948c  8236 793c f67e 8f0d 11da
Sent from /dev/tty1, please excuse my verbosity.
On air: Jadis - Live this lie (rewritten)
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: not available
URL: <http://alioth-lists.debian.net/pipermail/pkg-llvm-team/attachments/20220203/9d20797c/attachment.sig>