Getting them to pass distro muster is often harder but you don't need to do that. MacOS/FreeBSD will be different enough anyway that you will need to write a bunch more in install scriptīuilding simple package that just delivers binary is not even that complicated. ![]() RHEL/Centos RPM will cover near-whole rest of the market. deb will generally works fine under Ubuntu, Debian and most flavours just fine unless you have some funky dependencies (and if you do, installer will also be complex) > devs don't like packaging for every distro under the sun The effort to package is precisely what the complaint is about you have to tell (in package manifest) where your files land and which are app files (to be removed freely) and which are config (user might want to leave it, won't be automatically overwritten on update) ![]() Note that piping curl to bash or running bash on the output of curl/wget is a minor point quickly glossed over in the article, which is actually complaining much more about using custom installation scripts that do "too much". This includes things like associating file types with this program, changing system settings to make it default in various places (hopefully with some kind of flag, to be fair), discovering and associating hardware or any other step like that. ![]() You're not supposed to need to do any other configuration of your system for this program after the installer finishes in order to properly use it. It's there to copy files to your system and then modify your system so that it is ready to use the new program to the deepest level that makes sense. The author is complaining that it takes over their zsh configuration, when in fact that is obviously the whole point of the installer.Īn installer isn't simply there to copy a program to your system. ![]() This seems almost like a misunderstanding of what is the role of an installer, especially for something like oh my zsh.
0 Comments
Leave a Reply. |