07.01.2025 05:48, zhangdandan wrote:
...
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.

Please don't.  Please depend on qemu-system-loongarch64 instead of 
qemu-system-misc.
This works now, and this will work with any future split, and you wont need to 
change
anything in the future.  Also, please depend on particular architecture you're 
interested
in, not the qemu package name, because there's a chance we'll split things 
further.

qemu-system-loongarch64 provides this particular architecture emulation, this 
is what
you need and this is what you should depend on.

I wonder how the current dependencies in guestfs looks like..

 > 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.

It's always questionable where to draw the line between being its own thing or 
being
one of the "misc" things.  And it's somewhat depressing to be in the "misc" 
category.
For me, the line is simple: every architecture which is a release architecture 
in
debian, deserves the thing to be in its own package.

There are two more things to consider.  For me, I should remove 
qemu-system-sparc
package and stuff it into qemu-system-misc now, since sparc is not a debian 
release
architecture *anymore* (but it was in the past).  And for everyone else, - qemu 
is
moving towards single binary emulating ALL architectures.  So the whole split 
will
become a moot point entirely, as there will be just a single qemu-system 
package,
providing everything which all various qemu-system-foo packages providing now.

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.

This is exactly what works today: user is able to install 
qemu-system-loongarch64
package to obtain qemu-system-loongarch64 binary.  The fact that this package is
currently virtual does not really change anything, - the user needs to install
just the qemu architecture they are interested in.

Please depend on qemu-system-loongarch64 (of particular version if you need to),
and everything should be fine.

Thanks,

/mjt

Reply via email to