![]() ![]() I go ahead and add gitk and git-cvsserver to the new version entry. 1.8 has 5 git* programs, while 2.28 has 7. Looking at the two install locations, the programs slightly differ. Git is now installed to /usr/local/git/bin, but this is not on the $PATH so we will use alternatives again. If there are any build issues along the way, google the "X not found", or similar if the missing package is not obvious Note that they are sorted lexicographically instead of by release, so 2.28.0 come directly before 2.3.0 cd /usr/srcĪnd compile the source code, preparing to install to /usr/local/git cd git-2.28.0/ ![]() ![]() At the time of writing, this is 2.28.0, but check the link for newer/other versions. Then navigate to /usr/src (or a temporary folder if you don't plan on keeping the files) and download the latest from the Linux kernel archives and extract. Sudo yum install gcc perl-ExtUtils-MakeMaker $ cmake -versionįor this, we will install the latest version of git from source (mainly following their instructions), and then do the same process as before.įirst install dependencies sudo yum install curl-devel expat-devel gettext-devel openssl-devel zlib-devel slave /usr/local/bin/ccmake ccmake /usr/bin/ccmake3 \Īnd that's it, we're suddenly 7 years in the future. slave /usr/local/bin/cpack cpack /usr/bin/cpack3 \ slave /usr/local/bin/ctest ctest /usr/bin/ctest3 \ slave /usr/local/bin/ccmake ccmake /usr/bin/ccmake \Ĭmake3 sudo alternatives -install /usr/local/bin/cmake cmake /usr/bin/cmake3 20 \ slave /usr/local/bin/cpack cpack /usr/bin/cpack \ slave /usr/local/bin/ctest ctest /usr/bin/ctest \ Old cmake sudo alternatives -install /usr/local/bin/cmake cmake /usr/bin/cmake 10 \ These are combined as a family in the redhat implementation, which helps to group multiple masters together and handle one being deleted. I'm sure there are other opinions, but putting it in the "locally installed" folder makes the most sense to me.Īlong with the program itself, the associated programs are installed as slaves so the versioning is preserved across the group. 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 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |