2 ms·
FHS tries to stay relevant, but I'm not convinced it is. However the exact location is not the important point here. If no repository is available you should n
by xorcist 11y ago
FHS tries to stay relevant, but I'm not convinced it is. However the exact location is not the important point here.
If no repository is available you should not proceed with anything until you have a plan in place how to keep track of updates and security issues. How often do you update? Do you backport security issues or upgrade? There will be backwards incompatible changes upstream which fixes security problems, and you need to have a plan in advance when in panic mode.
And if no package is available you must first know why. Is it not supported? Is there a better way? What does that mean for your deployment? With this knowledge you create a package. Install it and keep a copy for future troubleshooting. Always use packages in Linux, unless you have a very good and specific reason not to.
Under no circumstances should you drop untracked files in your environment, unless it is a one man show.
- nailer 11y agoYep, this is why the article pushes packages as the preferable install method. Thankfully the unpackaged binaries are officially maintained and also frequently updated. I'm actually really surprised you showed up again. You made a post loudly proclaiming the lack of packaging, high availability, and Ansible in an article that had all those things, in the opening paragraphs. I'm trying to think of a polite way to say this, but: putting down someone else's work based on it missing things it actually includes (since you haven't bothered to read the article) is incredibly rude. Perhaps you forgot something in your most recent reply?