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

Wed Jul 13 14:00:57 UTC 2005

Author: ca3sar
Date: 2005-07-13 14:00:54 +0000 (Wed, 13 Jul 2005)
New Revision: 15736

Modified:
   lunar-doc/trunk/lunar-manual/inside_lunar.tex
   lunar-doc/trunk/lunar-manual/troubleshooting.tex
   lunar-doc/trunk/lunar-manual/using_lunar.tex
Log:
moving BUG section to troubleshooting, placeing kde, gnome, xfce in own section, removing module files like BUILD from toc in inside section

Modified: lunar-doc/trunk/lunar-manual/inside_lunar.tex
===================================================================

--- lunar-doc/trunk/lunar-manual/inside_lunar.tex	2005-07-13 12:04:41 UTC (rev 15735)
+++ lunar-doc/trunk/lunar-manual/inside_lunar.tex	2005-07-13 14:00:54 UTC (rev 15736)
@@ -65,55 +65,55 @@
 The \lstinline{lvu submit} command lets you send a changed or new module to the mailing list, where the developers take a look at it\footnote{Be sure to subscribe before doing so. See Chapter \ref{comty}}. If its good enough to be signed of it will be placed in the moonbase. See Chapter \ref{devel} for a more detailed discussion of module building. \par
 In \lstinline{/usr/share/doc/lunar} you can find a "skeleton" module to take a look at. \par
 
-\subsection{DETAILS}
+\subsubsection{DETAILS}
 
 Required for any module. This file contains the data needed to obtain, describe and update a package. In here vital information like download URL's, version numbers and package description is put.
 
-\subsection{DEPENDS}
+\subsubsection{DEPENDS}
 
 This file lists packages that need to be installed before you can install this package. It does not necessary have to be a library, but can also be include files or anything that you would need to compile, install and run the module. \par
 
 In here you can also list optional depends, being packages that do not necessary have to be installed, for instance packages that add extra features (e.g. fonts, plugins etc.).
 
-\subsection{CONFLICTS}
+\subsubsection{CONFLICTS}
 
 Modules listed in here must not be present when installing this module. Use this to separate your module from incompatible other ones. For instance the \lstinline{BitchX} module is incompatible with the gtk version \lstinline{gtkBitchX}, so these 2 modules have each other listed in their \lstinline{CONFLICTS} file. Another good example is conflicting daemons like \lstinline{sendmail} vs. \lstinline{exim}, \lstinline{cron} vs. \lstinline{hc-cron} etc. 
 
-\subsection{BUILD}
+\subsubsection{BUILD}
 
 This script will configure, make and install the package. You can virtually control everything in here, like adding patches (kernel), changing build options (xfree86) or asking the user for configuration options (sendmail). This script does not have to exist for programs that \lstinline{./configure && make && make install} (lin will automatically \lstinline{--prefix=/usr} for you), but a lot of modules need adjusting. 
 
-\subsection{CONFIGURE}
+\subsubsection{CONFIGURE}
 
 This file serves as an alternative way to customize the configuring of the package. 
 
-\subsection{PRE\_BUILD}
+\subsubsection{PRE\_BUILD}
 
 This file is used if you need to apply patches or modifications before the package is built. 
 
-\subsection{POST\_BUILD}
+\subsubsection{POST\_BUILD}
 
 Use this file if you need to tweak the compiles sources before it is installed.
 
-\subsection{PRE\_INSTALL}
+\subsubsection{PRE\_INSTALL}
 
 This file lets you prepare the installation process for the package. 
 
-\subsection{POST\_INSTALL}
+\subsubsection{POST\_INSTALL}
 
 When you need to additionally tweak things after installation, this is the place. Actions in this file are not logged in the install log, so you can e.g. create machine dependent configuration options that need to be kept in case of module removal. \par
 
 This is also the place to install and run daemons, reconfigure LILO etc..
 
-\subsection{PRE\_REMOVE}
+\subsubsection{PRE\_REMOVE}
 
 This script will be called before a module is lrm'ed. You can use it to back up configuration, stop daemons or similar stuff.
 
-\subsection{POST\_REMOVE}
+\subsubsection{POST\_REMOVE}
 
 Use this file to clean stuff up after removing a module, or place configuration files in a backup location, etc..
 
-\subsection{other files and directories}
+\subsubsection{other files and directories}
 
 Nothing withholds you from putting much more stuff in your module directory, think of patches, small scripts, init.d scripts, xinetd or pam.d configuration files, or funky ascii art to make your module install look nice. \par 
 

Modified: lunar-doc/trunk/lunar-manual/troubleshooting.tex
===================================================================
--- lunar-doc/trunk/lunar-manual/troubleshooting.tex	2005-07-13 12:04:41 UTC (rev 15735)
+++ lunar-doc/trunk/lunar-manual/troubleshooting.tex	2005-07-13 14:00:54 UTC (rev 15736)
@@ -39,6 +39,10 @@
 \textbf{Note} This is a small community and most developers  are rather busy. So please don't bug them until it bleeds. If nobody answers you in the chat, come back another day and use the other methods stated above to find a solution.\\
 \textbf{Note} Asking someone else is the way to learn less about an error. So this should be the last option for you to choose.
 
+\section{I found a BUG}
+
+If you found a bug in the Lunar Linux code, in a module or in the coretools, please fill out a bugreport on the website: \textit{http://bugs.lunar-linux.org} 
+
 \section{Frequently Asked Questions}\label{faq}
 
 \subsection{Compiler optimizations}

Modified: lunar-doc/trunk/lunar-manual/using_lunar.tex
===================================================================
--- lunar-doc/trunk/lunar-manual/using_lunar.tex	2005-07-13 12:04:41 UTC (rev 15735)
+++ lunar-doc/trunk/lunar-manual/using_lunar.tex	2005-07-13 14:00:54 UTC (rev 15736)
@@ -177,12 +177,11 @@
 
 \subsection{ Xorg}
 
-\subsection{K Desktop Environment}
+\subsection{Desktop Environments}
 
-\subsection{Gnome 2.6}
+\subsubsection{K Desktop Environment}
 
-\subsection{Xfce}
+\subsubsection{Gnome 2.6}
 
-\section{I found a BUG}
+\subsubsection{Xfce}
 
-If you found a bug in the Lunar Linux code, in a module or in the coretools, please fill out a bugreport on the website: \textit{http://bugs.lunar-linux.org} 
\ No newline at end of file

