Priority is a bit clunky, but the option with the highest priority is the default version. So now I will "install" both versions of cmaketo the alternatives directory by providing the path for the new program, new program name, original location, and priority. And scripts don't need to care about this strange naming. For my needs, 3.17 is sufficient so I will install cmake3 from yum sudo yum -y install cmake3īut now I have to type cmake3 every time I want to use cmake, and from practice I know muscle memory will hit enter before 3 every time without fail. At the time of writing this, cmake3 is version 3.17 and the latest is 3.18. This gist is mainly because I always forget how to do it when setting up a new system for myself, but it also shows a simple method for dealing with alternative versions of software CMakeĪ semi-updated version of cmake is available through yum, but named cmake3. It feels to me a lot like virtualenv in python $ git -version This allows for better package management and confines all sysadmin changes to the /etc directory, all while making switching back easier.
The alternatives essentially creates a symlink, but it actually is a symbolic link to the alternatives directory, which in turn is a symbolic link to the actual program. While this is still generally acceptable, there exists an alternative method (sorry).
I understand the eneterprise benefits, but configuring a development environment can be confusing, with most people using a combination of symlinks, adding folders to PATH, and enabling an scl_source Using up-to-date versions of software on RHEL is a pain. This should work on other Fedora-based distributions and for other packages, but I have not done extensive testing Introduction Installing the latest git/cmake versions on RHEL/Centos
0 kommentar(er)
