The answer for this guy and other people stretched by supporting Linux is to say it’s flatpak or nothing. Stop trying to build for each dist because it’s not sustainable. If someone on a dist wants to maintain a package then let them take the heat if it is broken.
If someone on a dist wants to maintain a package then let them take the heat if it is broken.
That’s quite literally what happened and why this guy is moaning though. Nobody asked him for an Arch build, people distribute it themselves on the AUR and he’s annoyed anyway.
I don’t think you quite understand how this works. No distro ever asks third party programmers to create packages for them—that’s the job of the distro’s own team, or of enthusiasts using the distro. All the distro packagers want or need from the original programmer is the source code and enough documentation to get it to compile. They take it from there.
Did you read the text? This guy was providing a package because the default one was broken and he’s fed up of dealing with complaints. And the solution to that is just flatpak the thing and tell users to use that regardless of dist.
I don’t think we can count the AUR repository as the “default package” because:
AUR is a community driven project, for users, by users. Repos are not maintained by the Arch team.
Arch user needs to explicitely get out of their way to access and use AUR, it is not enabled by default
AUR repos are not even packages (usually). They are build-instructions. There are specific -bin repos that provide packaged binaries, but that was not the case here, because the emulators license doesn’t allow that.
The issue here was that stenzek moved the emulator to a source-available license, which does not allow Arch to provide packages in their package repo. So people were using build instructions to build the emulator from source. And when that caused issues because something broke, people came to stenzek for support instead of the person maintaining the build instrucions.
And that’s the real fail. AUR users need to understand how things work, AUR packages are community maintained and supported. If the build fails, complain to the AUR maintainer, and they will raise the necessary bug reports to the upstream project if the bug is w/ the project instead of the build instructions.
Providing a package, if he did so, was his choice. No one at the distro asked him to (some users may have, but that has nothing to do with the distro or its other users). If you provide the package of your own volition, you should expect that there will be complaints if it doesn’t work as expected. You need a procedure (and a certain amount of saved-up mental fortitude) to deal with them.
If someone complains to you about someone else’s buggered-up packaging job, the correct thing to do is have a prewritten reply set up saying, “Nothing to do with me, complain to the other guy.” Then close the bugs as WONTFIX and get on with your life. And see if the package host has a removal policy for broken packages, if it is genuinely broken and not just clueless users messing up.
To me, this specific case seems like the dev wasn’t prepared for what the open Internet is like, couldn’t handle it, and imploded messily. Are the users that got on his nerves at fault? Yes, on one level, but their existence was also entirely predictable. If you know what you’re doing, you factor the existence of these people in when you decide whether you’re willing to release your software to the public or not and what communication channels you should leave open.
The answer for this guy and other people stretched by supporting Linux is to say it’s flatpak or nothing. Stop trying to build for each dist because it’s not sustainable. If someone on a dist wants to maintain a package then let them take the heat if it is broken.
Why should he get a say on how someone else installs the software on their own systems?
If I want to build an arch package instead, what business is that of his?
That’s quite literally what happened and why this guy is moaning though. Nobody asked him for an Arch build, people distribute it themselves on the AUR and he’s annoyed anyway.
I don’t think you quite understand how this works. No distro ever asks third party programmers to create packages for them—that’s the job of the distro’s own team, or of enthusiasts using the distro. All the distro packagers want or need from the original programmer is the source code and enough documentation to get it to compile. They take it from there.
Did you read the text? This guy was providing a package because the default one was broken and he’s fed up of dealing with complaints. And the solution to that is just flatpak the thing and tell users to use that regardless of dist.
I don’t think we can count the AUR repository as the “default package” because:
The issue here was that stenzek moved the emulator to a source-available license, which does not allow Arch to provide packages in their package repo. So people were using build instructions to build the emulator from source. And when that caused issues because something broke, people came to stenzek for support instead of the person maintaining the build instrucions.
And that’s the real fail. AUR users need to understand how things work, AUR packages are community maintained and supported. If the build fails, complain to the AUR maintainer, and they will raise the necessary bug reports to the upstream project if the bug is w/ the project instead of the build instructions.
Providing a package, if he did so, was his choice. No one at the distro asked him to (some users may have, but that has nothing to do with the distro or its other users). If you provide the package of your own volition, you should expect that there will be complaints if it doesn’t work as expected. You need a procedure (and a certain amount of saved-up mental fortitude) to deal with them.
If someone complains to you about someone else’s buggered-up packaging job, the correct thing to do is have a prewritten reply set up saying, “Nothing to do with me, complain to the other guy.” Then close the bugs as WONTFIX and get on with your life. And see if the package host has a removal policy for broken packages, if it is genuinely broken and not just clueless users messing up.
To me, this specific case seems like the dev wasn’t prepared for what the open Internet is like, couldn’t handle it, and imploded messily. Are the users that got on his nerves at fault? Yes, on one level, but their existence was also entirely predictable. If you know what you’re doing, you factor the existence of these people in when you decide whether you’re willing to release your software to the public or not and what communication channels you should leave open.
I use the Duckstation flatpak funny enough