Git clone that using the SSH method means that you won't have to answer the popups for user/password each time you do anything with the remote repo, although you will have to answer with a passphrase if you added one to your SSH key. If you already have a global address set up for other purposes, you may want to set a local config once you clone the Xastir repo: See the section "If Using Multiple GitHub Accounts" below. The email address should correspond to the address associated with your GitHub account. Make sure you've configured Git as shown above, particularly the name and email address commands. If you intend to contribute code to the Xastir project, there's going to be more to learn, but if you only want access to the latest sources, these few Git commands will be sufficient.Ī new README.GIT file exists in the source tree, just as there had always been a README.CVS. Note to developers only: "./update-xastir" is risky for you if you are modifying code: It uses "git pull". This will work if you don't need to pass any extra flags to "configure" for your particular Linux. Which will do EVERYTHING for you from the "git pull" to the "chmod" command. Note to developers only: "git pull" is risky for you if you are modifying code. Then compiling normally per the "Compiling and Installing Xastir" instructions shown above. Periodically, you can update the code by going into the repo directory and executing: Sudo chmod 4555 /usr/local/bin/xastir # Only needed if using kernel AX.25 # time: It removes debugging info from executable Sudo make install # "make install-strip" can be used after the first (make clean make -j3 2>&1) | tee make.log Mkdir -p build # Build in a separate directory Double check the requirements page, fix missing package issues, and start again. If you don't have Motif headers and libraries installed, configure will abort. If bootstrap.sh fails fails nothing will work. Notably, bootstrap.sh requires autoconf and automake, and this script is what produces the configure script used later. There is no point working through all the steps if you see error messages early on. If, at any point, you see error messages in the steps below, you have missing required packages. Make absolutely certain you have installed all prerequisite tools and libraries first. This will create an "Xastir" subdirectory, put a complete clone of the repository into it (including ALL branches and revisions!), and check out the "master" branch of the code. To obtain the Xastir repo for the first time: Git config -global core.whitespace "-trailing-space" Git config -global user.name "Your Name" user.email config -global color.ui auto Colorizing the Git output and having it ignore whitespace are niceties. The email address should correspond to the address associated with your GitHub account, but you don't need an account until you are a contributor to the project, or any GitHub project. The "git config" commands below are not strictly necessary, but if you ever try to make changes to Xastir and get them integrated with the project, the first command listed is quite important. Will let you know if you have it installed. To get a copy of the development repository, you must have "git" installed on your system. Git Instructions For Users Install and Configure Git 1.2.5 If Using Multiple GitHub Accounts.1.2.3 Important: Git Commit Message Format.
0 Comments
Leave a Reply. |