Dear mjt,
On Tue, 24 Dec 2024 15:29:15 +0300 Michael Tokarev wrote:
> Control: tag -1 moreinfo
> Control: severity -1 wishlist
>
> 24.12.2024 15:19, zhangdandan wrote:
> > Dear maintainer,
> >
> > We need to split out qemu-system-loongarch64 from qemu-system-misc
to qemu-system-loongarch64 package.
>
> 2 points.
>
> First, I'd love to have "generic" names for the cpu *families* in
package names.
> Like we have for ppc (which is a family name including several
different CPUs).
> "loongarch64" does not look like a family to me, more like a specific
architecture.
> Maybe "loongarch" would be better, but I don't know if it can be
confused with
> the 32bit loongarch.
>
> (yes I know we've s390x here, it was a (bad) historic precedent).
We agree with what you said.
I checked the definition of system-archlist-*(x86/arm/ppc/riscv/sparc)
in debian/control.mk.
Maybe "qemu-system-loongarch" would be better named as a software package.
> And second, for splitting things out of qemu-system-misc, I'd want
the architecture(s)
> in question to be in list of debian release architectures first, -
ie, not as a "port"
> architecture but as a regular fully supported architecture. This is a
clear criteria,
> or else we've discussions what should be in -misc and what should be
by its own.
If you think it is time to separate loongarch64 from misc, please remind
me, thanks.
we will update the patch in time.
> If the reason you want this split is because you want to *install*
something which will
> *provide* the needed binary, - you can do it today, by installing
qemu-system-loongarch64 -
> it is currently provided by qemu-system-misc. If you do this today,
you wont need to
> change your dependencies later, it wouldn't matter which package
actually provides the
> needed functionality, and it will continue to work even if we'll
merge all qemu-system
> subpackages into one qemu-system.
As you said, we can do it today, by installing qemu-system-loongarch64
-it is currently provided by qemu-system-misc.
The current status is: we add qemu-system-misc in other packages which
depend qemu-system-loongarch64 binary, e.g. libguestfs.
> So the real question is: *why* do you need to split
qemu-system-loongarch64 out?
Referring to other architectures supported by Debian QEMU, we think that
split qemu-system-loongarch64 out from misc is more in line with the
specifications of Debian QEMU.
At the same time, install qemu-system-loongarch{64} software package to
obtain qemu-system-loongarch64 binary, which is more in line with the
user's usage habits.
Your opinions are welcome.
Best regards,
Dandan Zhang
