Clarifying Paradigms for Installing Software
question
When it comes to installing software, I get the gist here.
However, I’m noticing that the project doesn’t always follow this itself. For instance, I need to install 1Password, for which there is an official Flatpak package. But I’m also noticing there’s a brew cask for it under the ublue project. It’s not clear to me what the reason for that is, but I assume it’s because of this? Perhaps it’s easier to work around the browser (and OS) integration issue with a brew installed binary? People are also installing the RPM via layer for CLI and browser integration. Just wanting to rationalize the “right way”, and understand reasoning for one vs the other when there are multiple paths like this. Thanks!
However, I’m noticing that the project doesn’t always follow this itself. For instance, I need to install 1Password, for which there is an official Flatpak package. But I’m also noticing there’s a brew cask for it under the ublue project. It’s not clear to me what the reason for that is, but I assume it’s because of this? Perhaps it’s easier to work around the browser (and OS) integration issue with a brew installed binary? People are also installing the RPM via layer for CLI and browser integration. Just wanting to rationalize the “right way”, and understand reasoning for one vs the other when there are multiple paths like this. Thanks!
