[Lunar-commits] r15628 - lunar-doc/trunk/lunar-manual

[ca3sar]

Author: ca3sar
Date: 2005-07-07 11:22:08 +0000 (Thu, 07 Jul 2005)
New Revision: 15628

Modified:
   lunar-doc/trunk/lunar-manual/6development.tex
   lunar-doc/trunk/lunar-manual/Lunar_Book.tex
Log:
changeing listing size to fit page

Modified: lunar-doc/trunk/lunar-manual/6development.tex
===================================================================
--- lunar-doc/trunk/lunar-manual/6development.tex	2005-07-07 10:58:19 UTC (rev 15627)
+++ lunar-doc/trunk/lunar-manual/6development.tex	2005-07-07 11:22:08 UTC (rev 15628)
@@ -35,7 +35,7 @@
 
 Every module is required to have at least a \lstinline{DETAILS} file. A minimal \lstinline{DETAILS} may appear as follows : (\lstinline{/var/lib/lunar/moonbase/editors/emacs/DETAILS}) \par
 
-\begin{lstlisting}
+\begin{lstlisting}[basicstyle=\tiny]
           MODULE=emacs
          VERSION=21.3
           SOURCE=$MODULE-$VERSION.tar.gz
@@ -54,7 +54,8 @@
 
 With comments, default values:
 
-\begin{lstlisting}
+
+\begin{lstlisting}[basicstyle=\tiny]
           MODULE=emacs                                      # Module name, yes it's redundant
          VERSION=21.3                                        # Version, changes *often*
           SOURCE=$MODULE-$VERSION.tar.gz                     # Source filename
@@ -85,7 +86,7 @@
 \lstinline{DEPENDS} may include both required and optional dependencies. The depends() function statement simply determines one required package. The \lstinline{optional_depends} function is a little more complex. It consists of the required package, necessary --options to give to\lstinline{ ./configure} (for yes and no respectively, and an explanatory comment telling the user the purpose of the option being presented. A typical \lstinline{DEPENDS} file might appear as follows : (\lstinline{/var/lib/lunar/moonbase/devel/subversion/DEPENDS})
 
 
-\begin{lstlisting}
+\begin{lstlisting}[basicstyle=\tiny]
 depends zlib    &&
 depends openssl &&
 optional_depends "db4" "--with-berkeley-db"  ""   "for creating local repositories"
@@ -94,7 +95,7 @@
 #     optional package       if "Y"       if "N"       explanatory comment
 #                       {  ./configure strings }
 \end{lstlisting}
-
+\lstset{basicstyle=\small}
 \subsubsection{The \lstinline{CONFLICTS} script}
 
 This script is simply used to specify modules which will be removed when a given module is installed. An example would be :  (\lstinline{/var/lib/lunar/moonbase/editors/elvis/CONFLICTS})
@@ -107,7 +108,7 @@
 
 The \lstinline{CONFIGURE} script is used to collect interactive input from the user on optional parameters for the software build. use the \lstinline'query' function and provide a default answer to each question. The results of the answers are then used to store configuration variables needed in configuration state files. An a simple example might be : (\lstinline{/var/lib/lunar/moonbase/crypto/gnupg/CONFIGURE})
 
-\begin{lstlisting}
+\begin{lstlisting}[basicstyle=\tiny]
 if ! grep -q CONFIGURED $MODULE_CONFIG ; then
   if query "Enable experimental external HKP keyserver interface? " n ; then
     OPTS="$OPTS --enable-external-hkp"

Modified: lunar-doc/trunk/lunar-manual/Lunar_Book.tex
===================================================================
--- lunar-doc/trunk/lunar-manual/Lunar_Book.tex	2005-07-07 10:58:19 UTC (rev 15627)
+++ lunar-doc/trunk/lunar-manual/Lunar_Book.tex	2005-07-07 11:22:08 UTC (rev 15628)
@@ -19,8 +19,9 @@
 \topmargin 0cm
 \selectfont
 \sf\sffamily
-\lstset{language=bash, numbers=left, numberstyle=\tiny, stepnumber=2, numbersep=5pt}
-%numbers at left side of source code, small, every 3 steps display on,  5pt away from code
+\lstset{basicstyle=\small, language=bash, numbers=left, numberstyle=\tiny, stepnumber=2, numbersep=5pt}
+%numbers at left  side of source code, small, every 3 steps display on,  5pt away from code
+%!!! For large code snippets this WILL be to large. pls invoke via : \begin{lstlisting}[basicstyle=\footnotesize]
 
 \begin{document}