[Cdd-commits] r1168 - projects/med/trunk/papers/09_osehc_porto
CDD Subversion Commit
noreply at alioth.debian.org
Wed Oct 29 15:22:53 UTC 2008
Author: tille
Date: Wed Oct 29 15:22:53 2008
New Revision: 1168
Modified:
projects/med/trunk/papers/09_osehc_porto/debian-med-bio.tex
projects/med/trunk/papers/09_osehc_porto/paper-text.tex
Log:
Section Methods
Modified: projects/med/trunk/papers/09_osehc_porto/debian-med-bio.tex
==============================================================================
--- projects/med/trunk/papers/09_osehc_porto/debian-med-bio.tex (original)
+++ projects/med/trunk/papers/09_osehc_porto/debian-med-bio.tex Wed Oct 29 15:22:53 2008
@@ -57,9 +57,9 @@
\newcommand{\myinsertgraphic}[1]{%
\ifpdf
% \resizebox{#2}{#3}{%
- %\resizebox{80mm}{53mm}{%
+ \resizebox{80mm}{53mm}{%
\includegraphics{#1}%
- %}%
+ }%
\else
\includegraphics{#1}%
%%\epsfig{file=#1.eps}%, height=#2, width=#3}
Modified: projects/med/trunk/papers/09_osehc_porto/paper-text.tex
==============================================================================
--- projects/med/trunk/papers/09_osehc_porto/paper-text.tex (original)
+++ projects/med/trunk/papers/09_osehc_porto/paper-text.tex Wed Oct 29 15:22:53 2008
@@ -23,10 +23,11 @@
\end{abstract}
\begin{tabular}{ll} % to become llll later
-Blend&Debian Pure Blend \\
-BTS& Bug Tracking System \\
-DFSG& Debian Free Software Guidelines \\
-LSB& Linux Standard Base \\
+Blend & Debian Pure Blend \\
+BTS & Bug Tracking System \\
+DFSG & Debian Free Software Guidelines \\
+GUI & Graphical User Interface \\
+LSB & Linux Standard Base \\
\end{tabular}
@@ -106,51 +107,23 @@
packaging: They are really the experts of the software in question and
we try to teach and help them in packaging.
-\section{Methods}
+\section{Methods}
\subsection{Unique technology supporting Debian's principles in packaging}
-
-\subsubsection{{\ttfamily .deb} packages}
-
-Most distributors ship their distribution in binary packages. Two
-package formats are widely used\cite{hess:2003}:
-
-\begin{description}
-\item[RPM (RedHat Package Manager)] which is supported by RedHat,
- SuSE, Mandrake and others.
-\item[DEB (Debian Package)] used by Debian and derived distributions.
-\end{description}
-
-It is this {\itshape adherence to policy\/} that causes a distribution
-to remain consistent within its own bounds. At the same time, this is
-the reason why packages can not always be safely installed across
-distribution boundaries. A SuSE \file{package.rpm} might not play well
-with a RedHat \file{package.rpm}, although the packages work perfectly
-well within their own distributions. A similar compatibility problem
-could also apply to packages from the same distributor, but from a
-different version or generation of the distribution.
-
-For Debian, all files of a program are packed as the \command{ar}
-archiver, otherwise known for the creation of programming libraries.
-Every such DEB package has a companion source package from which the
-binary package may be built automatically. The distributions of SuSE,
-RedHat and derivatives use the RPM format. The program
-\command{alien} by Joey Hess can translate between these. Though
-scripts to be run upon installation may get lost in the translation
-process.
-
-
\subsubsection{Build daemons}
-Sites external to the Debian main distribution may
-offer packages only for a subset of architectures.
-The Debian main distribution, however, automatically
-compiles software for all 11
-architectures that are supported by the Debian effort.
-To get a package into Debian, be it novel or an update of an existing package,
-the maintainer of a package submits the source code of the program together with his changes on the code to create the package. The build daemons (or autobuilders) compile the packages for each of the supported systems and make the resulting package publicly available for download. Logs of the build platforms are available online for everybody's inspection.
+Sites external to the Debian main distribution may offer packages only
+for a subset of architectures. The Debian main distribution, however,
+automatically compiles software for all 11 architectures that are
+supported by the Debian effort. To get a package into Debian, be it
+novel or an update of an existing package, the maintainer of a package
+submits the source code of the program together with his changes on
+the code to create the package. The build daemons (or autobuilders)
+compile the packages for each of the supported systems and make the
+resulting package publicly available for download. Logs of the build
+platforms are available online for everybody's inspection.
\subsubsection{Bug tracking system}
@@ -160,29 +133,30 @@
upstream developer, usually per email. A particular strength of
\printurl{www.sourceforge.net}{SourceForget.net} is to bring users of
a particular software together. Earlier than this effort was the
-\printurl{www.debian.org/Bugs}{Debian Bug Tracking System} (BTS).
-The maintainer of a software can decide if the bug should be forwarded to the upstream
-developers of the package or if it is fixed by himself. All problems are made
-public and hence the whole community may contribute to solving a particular issue.
+\printurl{www.debian.org/Bugs}{Debian Bug Tracking System} (BTS). The
+maintainer of a software can decide if the bug should be forwarded to
+the upstream developers of the package or if it is fixed by
+himself. All problems are made public and hence the whole community
+may contribute to solving a particular issue.
-\subsection{Divide and conquer of package maintenance}
+\subsection{Sharing the work}
The Debian Project is an association of individuals who share the
intention to create the best possible free operating system. This
-operating system that which is created is called Debian GNU/Linux, or
-simply Debian for short. Everybody in the internet may initiate a site
-and offer packages for the installation in Debian. A local administrator
+operating system that is created is called Debian GNU/Linux, or simply
+Debian for short. Everybody in the internet may initiate a site and
+offer packages for the installation in Debian. A local administrator
has to decide, if this public source may be trusted.
For Free Software development to work it requires a critical mass of
-supporters. Development without feedback prior to the submission of the
-final product is disadvantageous. The development of programs is not the
-main concern of a regular Linux Distribution. However, with the focus
-on Free Software and smooth local compilation, Debian considerably eases
-the contribution of comments and concise feedback of the technically skilled
-early adopters. Debian such helps to bring developers and users of
-applications together.
+supporters. Development without feedback prior to the submission of
+the final product is disadvantageous. The development of programs is
+not the main concern of a regular Linux Distribution. However, with
+the focus on Free Software and smooth local compilation, Debian
+considerably eases the contribution of comments and concise feedback
+of the technically skilled early adopters. Debian such helps to bring
+developers and users of applications together.
\begin{figure*}
\centering
@@ -199,7 +173,8 @@
community. When Debian developers first meet in person, they sign
each other's keys. Thus, the web of trust is woven.
-Debian does its best to have every member profit of somebody else's work as quickly as possible.
+Debian does its best to have every member profit of somebody else's
+work as quickly as possible.
\subsubsection{Debian Policy}
@@ -219,13 +194,13 @@
be located in \Path{/usr/share/doc/\$package}. CGI-scripts are
installed in \Path{/usr/lib/cgi-bin}.
-The policy statements are followed by the tool-chains and
-libraries used to build the software, and the lists of dependencies, which
+The policy statements are followed by the tool-chains and libraries
+used to build the software, and the lists of dependencies, which
dictate the prerequisites and order in which the software has to be
built and installed.
-Policies in Debian are developed within the community. Commonly with
-a single person or a small team drafting it, with further refinements
+Policies in Debian are developed within the community. Commonly with a
+single person or a small team drafting it, with further refinements
being discussed in respective mailing lists.
While every single maintainer of a Debian package has to build the
@@ -238,59 +213,49 @@
\subsection{Selection of packages}
-Debian contains nearly 10000 binary packages, and this number is
+Debian contains nearly 20000 binary packages, and this number is
constantly increasing. There is no single user who needs all these
-packages. The regular user is interested in a subset of these packages.
-To specify packages of one's particular interest, several options are
-provided by Debian:
+packages. The regular user is interested in a subset of these
+packages. To specify packages of one's particular interest, several
+options are provided by Debian:
\begin{description}
-\item[tasksel]
- Provision of a reasonable selection of rather general tasks that can
- be accomplished using a set of packages installed on a Debian
- GNU/Linux system. However, these are not yet covering scientific
- applications. The CDD toolkit which is currently developed will also
- support \command{tasksel} to enable selecting for instance
- Debian Med right after a fresh installation of a general Debian
- system.
-
-\item[standard package management]
- \command{dpkg} and \command{apt} provide means to search for
- packages of particular interest by its name or words in the
- package's description. Every package also indicates, as set by its
- maintainer, references to other packages of potential interest.
+\item[tasksel] Provision of a reasonable selection of rather general
+ tasks that can be accomplished using a set of packages installed on
+ a Debian GNU/Linux system. However, these are not yet covering
+ scientific applications. The Blend toolkit which is currently
+ developed will also support \command{tasksel} to enable selecting
+ for instance Debian Med right after a fresh installation of a
+ general Debian system.
+
+\item[command line package management] \command{apt} provide means to
+ search for packages of particular interest by its name or words in
+ the package's description. Every package also indicates, as set by
+ its maintainer, references to other packages of potential interest.
+
+\item[GUI] There are several graphical user interfaces to manipulate
+ the installation of packages on a Debian installation. The most
+ popular is currently \command{synaptic} which eneables users to seek
+ for certain packages and displays detailed information about each
+ package.
\end{description}
-
-In its current development, an ontology of applications of software,
-upon which semantical queries could be performed, analogous to
-Moby-S and \printurl{www.biomoby.org}{BioMoby} \cite{lord:2004,wilkinson:2005}
-effort, is not available.
-
-A package management system is a very strong tool to manage software
-packages on your computer. A large amount of the work of a
-distributor is building these software packages.
-The Debian package management tools have been ported to
-MacOS X\cite{fink:2005} and other Linux Distributions\cite{kojima:2000}.
-
Debian officially maintains 11 different architectures with many more
-not officially supported ports to other operating systems, which includes some
-that run another flavour of UNIX. Its
-technology for package management has been adopted for other operating
-systems, i.e. Fink on MacOSX
+not officially supported ports to other operating systems, which
+includes some that run another flavour of UNIX. Its technology for
+package management has been adopted for other operating systems,
+i.e. Fink on MacOSX
(\printurl{fink.sourceforge.net}{fink.sourceforge.net}).
-
-A {\itshape distribution\/} is a collection of software packages around the
-GNU Linux operating system that satisfies the needs of the target user
-group. There are general distributions, which try to support all
-users, and there are several specialised distributions, which each
-target a special group of users.
+A {\itshape distribution\/} is a collection of software packages
+around the GNU Linux operating system that satisfies the needs of the
+target user group. There are general distributions, which try to
+support all users, and there are several specialised distributions,
+which each target a special group of users.
{\itshape Distributors\/} are those companies that are building these
-collections of software around the GNU Linux operating system.
-Since the software is Free, the user who buys a distribution pays for
-the service that the distributor is providing. These services might
-be:
+collections of software around the GNU Linux operating system. Since
+the software is Free, the user who buys a distribution pays for the
+service that the distributor is providing. These services might be:
\begin{itemize}
\item Preparing a useful collection of software around GNU Linux.
\item Caring for smooth installation that the target user is able to
More information about the Cdd-commits
mailing list