[TutoNix]dim. juin 23 20:48:39 CEST 2019

slides.tex

@@ -480,14 +480,43 @@ The result of the build action is automatically placed into the nix store.
 
   \begin{enumerate}
   \item Applies functional paradigm to package management system.
-  \item Packages are derivations, written in Nix lang.
+  \item Packages are called derivations, written in Nix lang.
   \item The list of existing packages are into NixPkgs repository.
-  \item All build package are located into the store.
+  \item A built derivation is located to the nix store into a dedicated directory.
+  \item The folder name is generated from a hash of its inputs and its nix file.
   \end{enumerate}
 
 \end{frame}
 
-\begin{frame}{Why it is reproducible ?}
+\begin{frame}[fragile]{Why it is reproducible ?}
+  Writting a package for your application requires to state down every dependencies. \\
+
+  \vspace{1em}
+
+  The build process of your application is also incorporated within the derivation.
+
+\end{frame}
+
+\begin{frame}[fragile]{Why it is reproducible ?}
+  \vspace{1em}
+
+  The source of your application can be fixed:
+  \begin{lstlisting}[language=Nix,basicstyle=\small]
+  src = fetgit {
+    url = "https://gitlab.com/me/chord.tar.gz";
+    sha256 = "1h2jgq5pspyiskffq777nhi5rf0y8h...";
+  };
+  \end{lstlisting}
+
+  \vspace{1em}
+  The source of the Nixpkgs repository can be pinned.
+  \begin{lstlisting}[language=Nix,basicstyle=\small]
+{
+  pkgs ? import ( fetchTarball
+    "https://github.com/achive/e860b629bc0d1f9b.tar.gz" )
+  )
+}:
+  \end{lstlisting}
 
 \end{frame}