The program's documentation made no mention of that library. The program itself gave no message indicating it needed that library when clicking the icon it placed on my desktop. I had to open up a terminal window, manually type in the path of executable (hoping it would actually give me some feedback), interpret the feedback, go hunting around Yast2 and hope whatever OpenCL package I install was the right one.
The program itself requiring that library isn't dumb. The fact that the library isn't automatically installed with the program, is dumb. The fact that the program gave me no immediate feedback when attempting to start it, is dumb. The fact that I had to manually hunt around for the library in Yast, is dumb. DR is not a Tumbleweed package, so reporting that to the package maintainers isn't going to help anything.
In Windows, I install the program and it comes bundled with any libraries it needs. Same thing on OSX, same thing with Flatpaks.
Traditional package management is a failure because of maintenance burdens and the amount of software packages out there. You can't keep every package updated constantly, and you can't have every single piece of software in your repositories. You will ALWAYS run into the issues I described above with traditional package management.
The program itself requiring that library isn't dumb. The fact that the library isn't automatically installed with the program, is dumb. The fact that the program gave me no immediate feedback when attempting to start it, is dumb. The fact that I had to manually hunt around for the library in Yast, is dumb. DR is not a Tumbleweed package, so reporting that to the package maintainers isn't going to help anything.
In Windows, I install the program and it comes bundled with any libraries it needs. Same thing on OSX, same thing with Flatpaks.
Traditional package management is a failure because of maintenance burdens and the amount of software packages out there. You can't keep every package updated constantly, and you can't have every single piece of software in your repositories. You will ALWAYS run into the issues I described above with traditional package management.
Comment