If package makers do it wrong, shared libraries etc don't go where other programs expect to find them might endup duplicated, right? Same thing in Windows.

I like the dependencies stuff, checking if other programs are using stuff before uninstalling etc. But dumping all executables on one folder, all configuration files on another folder etc makes quite a mess, the other day i wasted a lot of time scrolling trying to find the executable for an specific program.....


IMO it makes much more sense to keep each thing in it's own folder, and if necessary add stuff to a list, symlink it or whatever to make other programs find it, or like i said, if the package manager is already keeping tabs of what is where, take advantage of that and read that data if you wanna know if a program is installed and where; relying on hardcoded paths is laziness...