[Cdd-commits] r1042 - cdd/trunk/dis/doc/en
CDD Subversion Commit
noreply at alioth.debian.org
Mon Aug 18 23:08:23 UTC 2008
Author: tille
Date: Mon Aug 18 23:08:23 2008
New Revision: 1042
Modified:
cdd/trunk/dis/doc/en/06_technology.sgml
Log:
More renaming / fixings
Modified: cdd/trunk/dis/doc/en/06_technology.sgml
==============================================================================
--- cdd/trunk/dis/doc/en/06_technology.sgml (original)
+++ cdd/trunk/dis/doc/en/06_technology.sgml Mon Aug 18 23:08:23 2008
@@ -8,13 +8,13 @@
<heading>Metapackage definition</heading>
<p>
-A metapackage, as used by CDDs, is a Debian package that contains:
+A metapackage, as used by DIShes, is a Debian package that contains:
<list>
<item>Dependencies on other Debian packages (essential)
<taglist>
<tag>Depends</tag>
<item><p>Use "Depends" for packages that are definitely needed
- for all basic stuff of the CDD in question.</p>
+ for all basic stuff of the DIS in question.</p>
</item>
<tag>Recommends</tag>
<item>The packages that are listed as "Recommends" in the
@@ -70,7 +70,7 @@
<var><cdd></var>-<var><task></var> where <var><cdd></var> stands for the
short name of a Debian Integrated Solution,
e.g. <package>junior</package> for Debian Jr. or <package>med</package>
-for Debian-Med, and <var><task></var> means the certain task inside the
+for Debian Med, and <var><task></var> means the certain task inside the
Debian Integrated Solution, e.g. puzzle or bio.
</p>
<p>
@@ -81,7 +81,7 @@
<tag><package>education-tasks</package></tag>
<item>Tasksel files for SkoleLinux systems</item>
<tag><package>med-bio</package></tag>
- <item>Debian-Med micro-biology packages</item>
+ <item>Debian Med micro-biology packages</item>
</taglist>
</p>
@@ -200,16 +200,16 @@
"<tt>med</tt>") and combine it reasonably with <prgn>grep</prgn>:
<example>
~> apt-cache search med | grep '^med-'
-med-bio - Debian-Med micro-biology packages
-med-common-dev - Debian-Med Project common files for developing...
-med-dent - Debian-Med package for dental practice client
-med-doc - Debian-Med documentation packages
-med-imaging - Debian-Med imaging packages
-med-imaging-dev - Debian-Med packages for medical image develop...
-med-tools - Debian-Med several tools
-med-bio-contrib - Debian-Med micro-biology packages (contrib an...
-med-common - Debian-Med Project common package
-med-cms - Debian-Med content management systems
+med-bio - Debian Med micro-biology packages
+med-common-dev - Debian Med Project common files for developing...
+med-dent - Debian Med package for dental practice client
+med-doc - Debian Med documentation packages
+med-imaging - Debian Med imaging packages
+med-imaging-dev - Debian Med packages for medical image develop...
+med-tools - Debian Med several tools
+med-bio-contrib - Debian Med micro-biology packages (contrib an...
+med-common - Debian Med Project common package
+med-cms - Debian Med content management systems
</example>
This is <strong>not really straightforward</strong>, and
absolutely unacceptable for end users.
@@ -225,43 +225,43 @@
grep -v '^Pri'
Package: med-imaging
Depends: paul, ctsim, ctn, minc-tools, medcon, xmedcon, med-common
-Description: Debian-Med imaging packages
+Description: Debian Med imaging packages
Package: med-dent
Depends: debianutils (>= 2.6.2), mozilla-browser | www-browser, ...
-Description: Debian-Med package for dental practice client
+Description: Debian Med package for dental practice client
Package: med-bio
Depends: bioperl, blast2, bugsx, fastdnaml, fastlink, garlic...
-Description: Debian-Med micro-biology packages
+Description: Debian Med micro-biology packages
Package: med-common
Depends: adduser, debconf (>= 0.5), menu
-Description: Debian-Med Project common package
+Description: Debian Med Project common package
Package: med-common-dev
Depends: debconf (>= 0.5)
-Description: Debian-Med Project common files for developing ...
+Description: Debian Med Project common files for developing ...
Package: med-tools
Depends: mencal, med-common
-Description: Debian-Med several tools
+Description: Debian Med several tools
Package: med-doc
Depends: doc-linux-html | doc-linux-text, resmed-doc, med-co...
-Description: Debian-Med documentation packages
+Description: Debian Med documentation packages
Package: med-cms
Depends: zope-zms
-Description: Debian-Med content management systems
+Description: Debian Med content management systems
Package: med-imaging-dev
Depends: libgtkimreg-dev, ctn-dev, libminc0-dev, libmdc2-dev...
-Description: Debian-Med packages for medical image development
+Description: Debian Med packages for medical image development
Package: med-bio-contrib
Depends: clustalw | clustalw-mpi, clustalx, molphy, phylip, ...
-Description: Debian-Med micro-biology packages (contrib and ...
+Description: Debian Med micro-biology packages (contrib and ...
</example>
This is, like the <prgn>apt-cache</prgn> example, <strong>also
a bit cryptic</strong>, and again is not acceptable for end users.
@@ -347,7 +347,7 @@
interface for package selection that is presented to the user
when installing a new computer. The <tt>End-user</tt> section
should contain an entry for each Debian Integrated Solution. This
- is currently the case for Debian-Jr.
+ is currently the case for Debian Jr.
<example>
Debian Task Installer v1.43 - (c) 1999-2003 SPI and others
@@ -448,7 +448,7 @@
<tag><url id="http://packages.debian.org/" name="Web search"></tag>
<item><p>Debian has a web interface that can be used to search for certain substrings
in package names. For instance if you are searching the meta
- packages of Debian-Med you could point your favourite Browser
+ packages of Debian Med you could point your favourite Browser
to</p>
<p>
<comment>FIXME: & is sometimes broken!!!
@@ -457,7 +457,7 @@
</comment>
<url id="http://packages.debian.org/cgi-bin/search_packages.pl?keywords=med-&subword=1">
</p><p>
- As a result you will get a list of all Debian-Med packages.
+ As a result you will get a list of all Debian Med packages.
</item>
<tag><url id="http://qa.debian.org/developer.php" name="Package Tracking System"></tag>
<item><p>
@@ -467,24 +467,24 @@
Debian user name of the developer who is responsible for the
metapackages:
<taglist>
- <tag>Debian-Jr:</tag>
+ <tag>Debian Jr:</tag>
<item>
<url id="http://qa.debian.org/developer.php?login=synrg">
</item>
- <tag>Debian-Med:</tag>
+ <tag>Debian Med:</tag>
<item>
<url id="http://qa.debian.org/developer.php?login=tille">
</item>
- <tag>Debian-Edu:</tag>
+ <tag>Debian Edu:</tag>
<item>
<url id="http://qa.debian.org/developer.php?login=pere">
</item>
<!-- currently no metapackages released for this project ...
- <tag>Debian-NP:</tag>
+ <tag>Debian NP:</tag>
<item>
<url id="http://qa.debian.org/developer.php?login=mako">
</item>
- <tag>Debian-Lex:</tag>
+ <tag>Debian Lex:</tag>
<item>
<url id="http://qa.debian.org/developer.php?login=terminus">
</item>
@@ -493,11 +493,11 @@
The other way to use the Package Tracking System is to search
for packages starting with a certain letter:
<taglist>
- <tag>Debian-Jr:</tag>
+ <tag>Debian Jr:</tag>
<item>
<url id="http://packages.qa.debian.org/j">
</item>
- <tag>Debian-Med:</tag>
+ <tag>Debian Med:</tag>
<item>
<url id="http://packages.qa.debian.org/m">
</item>
@@ -545,8 +545,8 @@
</list>
</p>
<p>
-Furthermore it is necessary to find a set of keywords for each Custom
-Debian Distribution and write a tool to search these keywords
+Furthermore it is necessary to find a set of keywords for each Debian
+Internal Solution and write a tool to search these keywords
comfortable. The best way to accomplish this might be to make use of
Debian Package Tags, which is a quite promising technique.
</p>
@@ -572,14 +572,14 @@
To accomplish this, a technique has to be implemented that allows to
define a set of users who get a task-specific menu while getting rid
of the part of software they are not interested in. Moreover this has
-to be implemented for certain groups of users of one Custom Debian
-Distribution, which are called "roles". There are several techniques
-available to manage user roles. Currently in the field of Custom
-Debian Distributions a UNIX group based role system is implemented.
-This means, that a user who belongs to a certain group of a Custom
-Debian Distribution is mentioned in the <file>/etc/group</file> file
-in the appropriate group and gets a special user menu that is
-provided for exactly this group.
+to be implemented for certain groups of users of one Debian Integrated
+Solution, which are called "roles". There are several techniques
+available to manage user roles. Currently in the field of Debian
+Integrated Solutions a UNIX group based role system is implemented.
+This means, that a user who belongs to a certain group of a Debian
+Integrated Solution is mentioned in the <file>/etc/group</file> file
+in the appropriate group and gets a special user menu that is provided
+for exactly this group.
</p>
<p>
Strictly speaking it is not the best solution to conflate a
@@ -594,14 +594,14 @@
may belong for the existing Debian Integrated Solutions at this time.
</p>
<p>
-In the long run, this role system might even be enhanced to
-certain "<em>levels</em>" a user can have and here the UNIX groups
-approach will definitely fail and has to be replaced by other
-mechanisms. This will include the possibility to enable the user
-adjust his own level ("novice", "intermediate", "expert") while only
-the administrator is able to access the UNIX groups. On the other hand
-such kind of user level maintenance is not only a topic for Custom
-Debian Distributions but might be interesting for Debian in general.
+In the long run, this role system might even be enhanced to certain
+"<em>levels</em>" a user can have and here the UNIX groups approach
+will definitely fail and has to be replaced by other mechanisms. This
+will include the possibility to enable the user adjust his own level
+("novice", "intermediate", "expert") while only the administrator is
+able to access the UNIX groups. On the other hand such kind of user
+level maintenance is not only a topic for Debian Integrated Solutions
+but might be interesting for Debian in general.
</p>
<p>
Another point that speaks against using UNIX groups for role
@@ -631,8 +631,8 @@
<package>cdd-common</package>. It has to be said that using
<prgn>cdd-update-menus</prgn> is not enough to change the menu of a
user. To accomplish this a call of the general
-<prgn>update-menu</prgn> script for every single user of a Custom
-Debian Distribution is necessary if this is not done by the
+<prgn>update-menu</prgn> script for every single user of a
+Debian Integrated Solution is necessary if this is not done by the
<file>postinst</file> script of a metapackage. This can easily been
done if the configuration file of a Debian Integrated Solution
<file>/etc/cdd/<var><cdd></var>/<var><cdd></var>.conf</file> contains the
@@ -668,7 +668,7 @@
----------------------
Here is a list of all normal users of the system. Now you can select those users who
-should get a Debian-Med user menu.
+should get a Debian Med user menu.
1. auser (normal user A) 6. fmeduser (med user F)
2. bmeduser (med user B) 7. glexuser (lex user G)
@@ -678,12 +678,12 @@
(Enter the items you want to select, separated by spaces.)
-:-! Please specify the Debian-Med users! 2 8
+:-! Please specify the Debian Med users! 2 8
</example>
This example shows the situation when you
<prgn>dpkg-reconfigure</prgn> <package>med-common</package> if
<var>med user B</var> and <var>med user H</var> were defined as users
-of Debian-Med previously and <var>med user F</var> should be added to
+of Debian Med previously and <var>med user F</var> should be added to
the group of medical staff. (For sure it is more convenient to use the
more comfortable interfaces to <package>debconf</package> but the used
SGML DTD <url id="http://bugs.debian.org/140684" name="does not yet
@@ -704,7 +704,7 @@
<tag><package>cdd-dev</package></tag>
<item><p>Helpful tools to build metapackages from a set of template
files. These tools are interesting for people who want to
- build metapackages in the style Debian-Edu and Debian-Med
+ build metapackages in the style Debian Edu and Debian Med
are currently doing this. The purpose of this package is to
make maintenance of metapackages as easy as possible.</p>
<p>This package is described in detail in appendix <ref
@@ -730,7 +730,7 @@
<heading>Other interesting tools</heading>
<sect1 id="simple-cdd">
- <heading>Simple-CDD</heading>
+ <heading>Simple-DIS</heading>
<p>
The tool <prgn>simple-cdd</prgn> is a limited though relatively easy
More information about the Cdd-commits
mailing list