Hi Talha,
On 2026-03-13 12:13, Talha Can Havadar wrote:
> I also have questions regarding the need of fork for ROCm. Why
> we are not using build profiles to build for rocm. I started
> experimenting this and the only conlict I see so far due to gloo-rocm
> (again forked from src:gloo) I think we could apply the same build
> profile logic to there as well. I am working on a PoC to see if that
> works. If it works it will require changes in src:gloo as well.
If, by this, you mean:
(1) have one src:pytorch, with multiple build profiles
(2) build and upload the ROCm variant via such a profile, instead of
a source fork
Then sadly I don't think this will work, because the autobuilder network
will not build with such profiles. Furthermore, this goes against the
general expectation that one can just do `apt-get source` and
`dpkg-buildpackage` to get the same binary result.
I tried something similar for ggml [1] and ultimately had to drop this
again [2], for the above reasons.
Best,
Christian
[1]: https://lists.debian.org/debian-ai/2025/12/msg00083.html
[2]: https://lists.debian.org/debian-ai/2025/12/msg00097.html
