Arch Linux User Repository

@Lawstorant Regardless of timing, the request to make firmware optional was independently valid. This package includes a module xone-wired that does not require the firmware.

The request to make firmware optional coincides wit the date where you took over the maintaining of the firmware packages and added like a million haskell dependencies by mistake. I could understand if that WERE still the case.

Whether firmware is optional makes no difference to me, but I wouldn't characterize it as a "mistake". It's common for modules and firmware to be split with only optdeps connecting them. Installing firmware is ultimately user responsibility, which some might even prefer to manage without an additional AUR package. I assume the user who requested that the firmware be made optional is managing fine without it.

Switching forks will be considered when the stable package stops working. Feel free to flag it when that happens. Before then, there's no need to force people who still want to use the medusalix version to switch.

And I must say, I do not agree with the notion that the firmware is optional. It's not just for wireless controllers, but for everything wireless (like headsets) and the vast majority of supported devices are wireless.

Another thing is that the driver doesn't handle missing firmware cleanly and still asks for it. It's in no way designed to work with the firmware missing just like other drivers that rely on firmware (amdgpu is one such example).

That fact that it's a separate package comes solely to licensing differences.

I think making it optional was a mistake.

Okay, it will be broken in about 6-7 weeks when 6.15 lands as 6.15 introduced breaking changes. I already created a fix for the active fork. I don't think keeping it alive longer that that would make sense. dlundqvist should just create 0.4.0 release soon.

The firmware is required for the wireless controller, but some people with wired controllers want to build fewer packages.

As far as the stable package is concerned, it can stay pinned to the medusalix repo until people start complaining that it isn't working anymore.

@xiota why is the dongle firmware an optional dependency? It's required to work.

@dlundqvist this is open source. This is how software lives. One project stops due to author/team going MIA, a fork picks up and continues. Nothing icky about that!

Hey, I'm the owner of the xone fork. I'm hesitant to make a proper release without a handover from original author. I don't want to make it look like I'm hijacking the project in any way. I have not tried to get in contact with medusalix but perhaps it's time for that...

This package switched forks because development on the original has stalled. For those who prefer, aur/xone-dkms is pinned to the last commit from medusalix. However, the stable package would also switch forks if dlundqvist makes an actual release because that would signal continued development from medusalix to be highly unlikely.

I did not experience any difficulties with this package requiring reboot. Perhaps there was a concurrent kernel update? As for having to disconnect and reconnect devices, doing so is not particularly unusual and may be needed for a variety of devices and circumstances.

The dlundqvist package redirects to this one and will eventually be retired.