+
+\begin{lstlisting}[language=bash]
+ $ cd /<repo home>/cin5
+ $ git pull
+\end{lstlisting}
+
+\paragraph{Useful git commands}%
+\label{par:useful_git_commands}
+
+
+\begin{lstlisting}[language=bash]
+$ git clone "git://git.cinelerra-gg.org/goodguy/cinelerra.git" cin5
+$ git pull # pull remote changes to the local version
+$ git status # shows changed files
+$ git clean -i # interactive clean, use answer 1 to "clean"
+\end{lstlisting}
+
+
+
+\subsection{How to Build from a Previous GIT Version}%
+\label{sub:how_to_build_from_a_previous_git_version}
+
+
+\begin{lstlisting}[language=bash]
+$ cd /<path>/cin5_repo
+$ git log
+$ git checkout <version>
+\end{lstlisting}
+
+
+The “git log” command produces a log file with hash values for commit keys. The hash ids are the commit names to use when you use git checkout.
+Next is displayed sample output:
+
+
+\begin{lstlisting}
+delete stray line in last checkin
+
+commit 4a90ef3ae46465c0634f81916b79e279e4bd9961
+Author: Good Guy <good1.2guy@gmail.com>
+Date: Thu Feb 22 14:56:45 2018 -0700
+
+nested clips, big rework and cleanup, sams new icons, leaks and tweaks
+
+commit f87479bd556ea7db4afdd02297fc00977412b873
+Author: Good Guy <good1.2guy@gmail.com>
+Date: Sat Feb 17 18:09:22 2018 -0700
+\end{lstlisting}
+
+For the “git checkout <version>, you would then keyin the line below for the following results:
+
+\begin{lstlisting}
+$ git checkout f87479bd556ea7db4afdd02297fc00977412b873
+
+Note: checking out 'f87479bd556ea7db4afdd02297fc00977412b873'.
+
+ You are in 'detached HEAD' state. You can look around, make experimental
+ changes and commit them, and you can discard any commits you make in this
+ state without impacting any branches by performing another checkout.
+
+ If you want to create a new branch to retain commits you create, you may
+ do so (now or later) by using -b with the checkout command again. Example:
+
+ git checkout -b <new-branch-name>
+
+ HEAD is now at f87479bd... more file size icon updates, and more to followend
+\end{lstlisting}
+
+Later to get the repo back to current, use:
+\begin{lstlisting}
+$ git checkout master
+\end{lstlisting}
+
+
+\subsection{Debuggable Single User Build}%
+\label{sub:debuggable_single_user_build}
+
+
+To build from source with full debugging symbols, first build a full static (non\_debug) build as follows but instead /tmp substituted with a permanent disk path if you want to keep it.
+
+\begin{lstlisting}
+$ git clone ...
+$ cp -a /path/cinelerra-5.1 /tmp/.
+$ cd /tmp/cinelerra-5.1
+$ ./bld.sh
+\end{lstlisting}
+
+
+Then, to run as a developer in the debugger:
+
+\begin{lstlisting}[language=bash]
+$ CFLAGS=”-O2 -ggdb” make -j8 rebuild_all
+$ cd cinelerra
+$ gdb ./ci
+\end{lstlisting}
+
+
+\subsection{Unbundled Builds}%
+\label{sub:unbundled_builds}
+
+There are some generic build scripts included in the Cinelerra-GG GIT repository for users who want to do unbundled builds with ffmpeg already available on their system.
+This has been tested on Arch, Ubuntu 18, FreeBSD, and Leap 15 (rpm) at the time this was documented.
+The names of the build scripts are: arch.bld , bsd.bld , deb.bld , and rpm.bld .
+These scripts are in the “blds” subdirectory.
+The bsd.bld should be used with the bsd.patch file in that same directory.
+
+The reason that Cin Infinity traditionally uses thirdparty builds (bundled builds) is because there are a lot of different distros with varying levels of ffmpeg and other needed thirdparty libraries.
+However, some users prefer using their current system baseline without another/different copy of ffmpeg.
+With different levels of the user’s libraries, uncertainty, potential instability, and unknown issues may come up while running Cinelerra and this will make it, for all practical purposes, impossible to diagnose and debug problems or crashes.
+There may be no help in these cases. You are encouraged to report any errors which potentially originate from Cin Infinity, but if the data indicates alternate library sources, please report the problems to the appropriate maintainers.
+
+With the unbundled builds, some features may not be available and no attempt to comment them out has been made.
+So if you use a pulldown, or pick a render option, or choose something that is not available, it just will not work.
+For example, unless special options were set up by you, the LV2 audio plugins will not be available.
+Nor will the codec libzmpeg, the file codec ac3, or DVD creation.
+The old school file classes will all work, but some of the formats that come with ffmpeg may not because of the way that ffmpeg was installed on your operating system.
+That is because the Cinelerra ffmpeg is a known static build and is usually the latest stable/released version.
+In the current case of Leap 15, libx264 and libx265 are not built in and this can be debilitating; You can always run “ffmpeg -formats” and “ffmpeg -codecs” to see what is available on your system.
+
+
+\section{Download Already Built Cinelerra-GG}%
+\label{sec:download_already_built_cinelerra_gg}
+
+If you prefer to not have to take the time to build Cinelerra-GG Infinity yourself, there are pre-built dynamic or static binaries for various versions of ubuntu, mint, suse, fedora, debian, centos, arch, and slackware linux as well as Gentoo and FreeBSD.
+There are also 32-bit i686 ubuntu, debian, and slackware versions available.
+These are updated on a fairly regular basis as long as significant code changes have been made.
+They are in subdirectories of:
+
+\url{https://cinelerra-gg.org/download/tars}
+
+\url{https://cinelerra-gg.org/download/pkgs}
+
+The “\textbf{tars}” directory contains single-user static builds for different distros.
+This is the recommended usage of Cinelerra-GG because all of the files will exist in a single directory.
+To install the single user builds, download the designated tarball from the ./tars subdirectory and unpack as indicated below:
+
+\begin{lstlisting}[language=bash]
+$ cd /path
+$ mkdir cin
+$ cd cin
+$ tar -xJf /src/path/cinelerra-5.1-*.txz # for the *, substitute your distro tarball name
+\end{lstlisting}
+
+Do NOT download the LEAP 10-bit version unless you use h265 (it can't render 8-bit h265).
+
+The “\textbf{pkgs}” directory contains the standard packaged application for various distros.
+This will install a dynamic system version for users who prefer to have the binaries in the system area and for multi-user systems.
+In addition, performing the package install checks the md5sum in the file md5sum.txt to ensure the channel correctly transmits the package.
+There is a README.pkgs file in the “pkgs” directory with instructions so you can “cut and paste” and avoid typos; it is also shown next.
+
+%TODO point to real READ.pkgs