added pycharm git cloning and restructured working with packages into ecosystems part

Author: thomasWeise

bookbase

@@ -177,9 +177,15 @@
 So even correct program output does not guarantee that the program itself is correct.
 Therefore, always checking each and every piece of code that your \pgls{IDE} marks as dodgy is very important.
 Make sure that you full understand all error and warning messages.
-Always fix them when necessary (obviously).
+
+Warnings can be important, too.
+They can indicate possible errors, potential problems with variable types, or missing required packages (see, e.g., \cref{sec:gitClonePycharm}).
+Always fix errors and warnings wherever possible (obviously).
 Even where you deem the warnings as false-positives, try to fix them anyway.
-On one hand, \emph{you} might wrong on.
+They could result from non-standard code formatting that still \inQuotes{works}, but may be confusing for readers of your code.
+You should always try to produce warning-free code.
+For every warning or error that you deem as not a problem, remember:
+On one hand, \emph{you} might wrong.
 On the other hand, having fewer warnings and false-positive suspected errors makes it easier to find the actual problem if an actual problem happens.%
 %
 \FloatBarrier%

text/main/basics/variables/errorsInIde/errorsInIde.tex

@@ -0,0 +1,12 @@
+\hsection{Working with the Ecosystem}%
+%
+A software developer rarely works on a stand-alone project all by themself.
+Instead, they develop projects that are part of an ecosystem of applications.
+Their programs will usually depend on libraries, i.e., \python\ packages that offer functionality.
+Often, their projects are stored in \pglspl{VCS} like \git\ repositories.
+In this part of the book, we will take a small glimpse on how to work within a system of existing projects and \pglspl{VCS}.%
+%
+\hinput{packages}{packages.tex}%
+\hinput{git}{git.tex}%
+%
+\endhsection%

text/main/ecosystem/ecosystem.tex

@@ -0,0 +1,15 @@
+\hsection{The Distributed Version Control System git}%
+%
+Today, \git~\cite{S2023LG,T2024BGAGVCPMATFTND} is maybe the \pgls{VCS} with the most wide-spread use.
+It is the \pgls{VCS} on which \github~\cite{PRGWSUdVLFTEKPKFBV2016TSRFTAOGAG} is based, which, in turn, is maybe the most important hub for open source software projects in the world.
+\git\ is based on a \pgls{clientServerArchitecture}, where the \pgls{server} hosts and manages repositories of source code and other resources.
+The \git\ \pgls{client} is a command line application that is run in the \pgls{terminal} and which allows you to clone (i.e., download) source code repositories and upload (i.e., commit) changes to them.
+A repository is something like a directory with files and their editing history, i.e., you can work and improve source code, commit changes, and see the history of all past commits.
+This is what \pglspl{VCS} are for:
+They do not just provide the current state of a project and allow teams to cooperative and continuous develop software, they also store the history of the project so as to enable us to see which code was used in which version of our software and to track changes.
+How to correctly use \git\ thus is a very complex and involved topic beyond the scope of this book.
+However, we will here take at least a look into a very small subset of functions that provide you a starting point for working with \git\ repositories.%
+%
+\hinput{gitClone}{gitClone.tex}%
+%
+\endhsection%

text/main/ecosystem/git/git.tex

@@ -0,0 +1,16 @@
+\hsection{Cloning git Repositories}%
+%
+The most fundamental activity you will encounter is \emph{cloning} repositories.
+Under \git, this basically means to download the complete repository and its history to your machine.
+You can now make local changes to the downloaded files.
+You can create commits, that will change the local version of your repository.
+Then you could push these changes back to the repository hosted by the \git\ \pgls{server}, making them accessible for other users.
+But, well, the first step is to clone - i.e., to download -- the repository.
+
+You can clone \git\ repositories with the command line \bashil{git} \pgls{client} program.
+However, \pycharm\ also has a \git \pgls{client} built in.
+We here outline both approaches.%
+%
+\hinput{gitClonePycharm}{gitClonePycharm}%
+%
+\endhsection%

text/main/ecosystem/git/gitClone/gitClone.tex

@@ -1,5 +1,6 @@
 %
 \hsection{Using Packages}%
+\label{sec:usingPackages}%
 %
 \begin{figure}%
 \centering%

text/main/ecosystem/git/gitClone/gitClonePycharm/gitClonePycharm.tex

@@ -194,7 +194,7 @@
 \begin{sloppypar}%
 Finally, in our example in \cref{lst:packages:numpy_user_venv_sh,fig:venvLinux8}, we delete the \pgls{virtualEnvironment} directory again via~\bashil{rm -rf .venv}.
 Normally, you would \emph{not} do this.\footnote{%
-I just clean up here because my examples are automatically executed whenever the book is built and I want to avoid that the examples interfer with each other or that, accidentally, some files from the environment land in my \git\ repositories.}%
+I just clean up here because my examples are automatically executed whenever the book is built and I want to avoid that the examples interfer with each other or that, accidentally, some files from the environment land in my \git\ repositories.}
 You do not want to re-create the \pgls{virtualEnvironment} again every time you execute your application.
 As said, once you have installed the required \pglspl{package}, you can simply activate the environment and run your program whenever you want.%
 \end{sloppypar}%

text/main/ecosystem/git/gitClone/gitClonePycharm/gitClonePycharm01website.png

@@ -1,5 +1,6 @@
 %
-\hsection{Requirements Files}
+\hsection{Requirements Files}%
+\label{sec:requirementsFiles}%
 %
 \gitPython{\programmingWithPythonCodeRepo}{packages/requirements.txt}{--args format}{packages:requirementstxt}{%
 A requirements file demanding that version~\textil{1.26.4} of \numpy\ be installed.}%

text/main/ecosystem/git/gitClone/gitClonePycharm/gitClonePycharm02copyUrl.png

@@ -1,5 +1,6 @@
 %
 \hsection{Virtual Environments in PyCharm}%
+\label{sec:venvAndPycharm}%
 %
 \begin{figure}%
 \centering%
@@ -78,6 +79,7 @@
 The \pgls{IDE} \pycharm\ also supports using \pglspl{virtualEnvironment} and \textil{requirements.txt} files.
 Let us here demonstrate this on the example program that requires \numpy\ which was given as \cref{lst:packages:numpy_user} and \textil{requirements.txt} file given in \cref{lst:packages:requirementstxt}.
 In \cref{fig:venvPycharmA}, we work through the steps to create and manage a project with a \pgls{virtualEnvironment} in \pycharm\ on their basis.
+(A complete example on how to copy a source code repository from \git\ or \github\ and how to set up a \pgls{virtualEnvironment} for its dependencies is given in \cref{sec:gitClonePycharm}.)
 
 First, we need to create a new project~(\cref{fig:venvPycharm1}).
 For this purpose, we already copied the files \pglspl{virtualEnvironment} and \textil{requirements.txt} into a folder~(here:~\textil{/tmp/packages}).

text/main/ecosystem/git/gitClone/gitClonePycharm/gitClonePycharm03copiedUrl.png

@@ -6,5 +6,5 @@
 \hinput{basics}{basics.tex}%
 \hinput{controlFlow}{controlFlow.tex}%
 \hinput{classes}{classes.tex}%
-\hinput{packages}{packages.tex}%
+\hinput{ecosystem}{ecosystem.tex}%
 %