The problem with a distribution-agnostic approach is tossing distribution policy into /dev/null means instead of maintainers and admins and users and devs havin

The problem with a distribution-agnostic approach is tossing distribution policy into /dev/null means instead of maintainers and admins and users and devs having to learn the one, probably fairly complicated, policy, or more likely numerous policies for various distros, instead msdos era anarchy is unleashed on the world. https://www.debian.org/doc/debian-policy/ https://www.debian.org/doc/debian-policy/ Sections 6 thru 12 are what it means to be "a Debian" rather than say freebsd packaged into .deb files. For some very end user applications that don't interact in any way with anything else, games perhaps, that works pretty well, until something is run into that does need to interact with other components also operating under the same anarchy. The problem with not having a closed system or standard or method of operating a system aka an operating system, is you end up with the deployed machines having an Apocalypse Now quote conversation "Are my methods unsound?" "I don't see any method at all, sir." If you're a system Administrator what does it mean to Administrate mere anarchy?