New comment by dmarto on void-packages repository

https://github.com/void-linux/void-packages/pull/36086#issuecomment-1066158102

Comment:
Hey, thanks for the suggestion, honestly I was split between several options:
 - this one, that should cover everything and hopefully work (based on my knowledge of xbps)
 - having both iotop pkgs conflict with one another, and adding some info in the pkg desc
 - what you suggested and using another name for the binary and keeping the old pkg as is
 - removing the old one and leaving only the iotop-c

I ended up on this path, as I don't feel the other two are proper or quality solutions.

---

My "view" of the process, may be very, very wrong, but "It worked on my Machine (ТМ)" :D

The old iotop is replaced before the new one; and thanks to the `conflicts` of the c-iotop pkgs, the group can't be registered before the old one gets handled by its own pkg and registers the group. That way, there is no need to worry about order of operations.

Anyway, I am willing to wait on a comment from the guys that better know the internals of xbps and figuring out a way to make it work with `alternatives` - as the OG iotop is a de-facto standard and well at least in some cases I can see the preference to have them both.