On 2/17/25 20:07, Cordell Bloor wrote:
If the documentation is identical for both the ROCm and CUDA versions of magma, do we want to just move libmagma-doc from contrib into main instead of creating a new libmagma-rocm-doc package? I suppose if the ROCm and CUDA versions of the package are different versions, you might want to be able to install both versions of the docs, but it does seem a bit odd to have two practically identical packages. I could see a case for doing it either way.
I'd prefer separated documentation packages, even if they are kind of duplicate. This gives flexibility, while intertwined package may lead to inconsistency or blockage.
For example, if I encountered some build issue with the cuda version and cannot fix it timely. In that case the rocm variant can still be updated independently, and you are not forced to fix the cuda build to make the rocm variant complete or consistent. Different variants can be prepared asynchronously. Such case also leads to version difference in doc packages, and you do not want a doc package for a mismatched older/newer version.
Similarly, by separating src:pytorch and src:pytorch-cuda, I would not worry about any potential cuda build issue and it does not block the updates to the CPU version. Isolation makes things safer and easier to prepare than a giant update with everything ready.
