Bug#1129598: magma: Should we have single src:magma for all instead of (auto) forked src:magma-rocm?

[Talha Can Havadar]

Package: magma
Severity: wishlist

Dear Maintainer,

We recently needed to touch src:magma and src:magma-rocm on Ubuntu to patch it to support ROCm 7
on version 2.9.0. While current way of working fine for most time, it increases overhead for
maintenance when there is a need for it. 

Today, if we want a fix specifically for src:magma-rocm, ideally we should go through src:magma
then generate src:magma-rocm from src:magma.

But I was thinking why we are not using multiple builds in single source package as an option, like
we see in src:curl.

I would like to hear your thoughts on this matter and if you think that is something we could try
I am willing to spend my time on it to make this a thing for src:magma.

Looking forward to hear from you!

Best Regards,
Talha

-- System Information:
Debian Release: forky/sid
  APT prefers resolute
  APT policy: (500, 'resolute')
Architecture: amd64 (x86_64)

Kernel: Linux 6.19.0-6-generic (SMP w/16 CPU threads; PREEMPT)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) (ignored: LC_ALL set to C.UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled