A bit of text.

2 files changed, 16 insertions, 2 deletions

diff --git a/main.pdf b/main.pdf
index c814e40..ec33174 100644
--- a/main.pdf
+++ b/main.pdf
diff --git a/main.tex b/main.tex
index 8d6d374..573aaae 100644
--- a/main.tex
+++ b/main.tex
@@ -67,6 +67,16 @@
 \end{minted}
 \end{minipage}
 
+\note[item]{The other solution is hard-coded, so whenever
+  anything changes, everything has to be changed again. Other
+  solution is the same as what we used to use for Python 2 (and
+  we still use for Python2 in some enterprise channels), and it
+  is the same now when we use it for simultaneous support of
+  Python 3.8, 3.9, 3.10 and possibly soon 3.11 on Tumbleweed,
+  and it would be the same if somebody finally fixed pypy3 or if
+  a miracle happened and somebody got jythohn to the functional
+  state.}
+
 \end{frame}
 
 \begin{frame}[fragile]
@@ -172,13 +182,17 @@ export NOBUMPA=1
 \end{frame}
 
 \begin{frame}
-    \frametitle{Not enough checking}
+    \frametitle{Toil to machines!}
 
     \begin{itemize}
         \item Given the number of packages we maintain (over
             2,500 in Factory) we need to put as much work as possible
             on machines.
         \item Packages are auto-generated by `py2pack`.
+        \item Automatic rebuilds
+        \item Every build in openSUSE ecosystem is checked by
+            rpmlint and unless specifically permitted, failed
+            rpmlint check means failed build.
     \end{itemize}
 
 \note[item]{They are auto-generated, but they are more like a
@@ -187,6 +201,7 @@ export NOBUMPA=1
   \texttt{pyp2rpm}, but we have never managed to unify two
   code-bases. If anybody is willing to do the work, it would be
   lovely.}
+\note[item]{I may add an anecdote about }
 
 \end{frame}
 
@@ -199,5 +214,4 @@ export NOBUMPA=1
 
 \end{frame}
 
-
 \end{document}