![]() There are many good reasons to use a package manager. I don't think an admin doesn't know what they are doing because they don't choose to use package management. Today's admins really don't know what they are doing, because theyĭon't do things from scratch and instead prefer package management. In this case the easiest way is to build a repository of your own, build your own packages based on the source code of the latest version, and then use again the package manager on each server to update the packages using your repository. However the problem is bigger if you have to administer more than 1 server. It is time consuming, and you have to constantly monitor if a new version gets out with security bugs. This is very useful in a production server, since you spend your time in system administration, auditing etc, rather than constantly checking if a package has a new update.Ģ) If your project needs the latest features that only the latest versions - of the applications you need - provide, then you have to compile everything from source. Most famous distributions (Redhat, Centos, debian) keep the official packages constantly updated, since they backport all security patches, and you don't have to worry about security updates, since they can be updated automatically. It installs automatically all dependencies, and your work is limited in the configuration files. There is no excuse to the ease the package system provides. However, as everything in life, deciding which method one should use, is based on one's requirements:ġ) If the official distribution's package versions cover your needs for features, then the answer is clear: Use the package system. Surely, a system administrator has to know how to compile from source, and it is very rare that one has not done it at least once. ![]() ![]() ![]() I believe that this statement is not accurate. ![]()
0 Comments
Leave a Reply. |