[Cdd-commits] r1233 - in blends/trunk: blends/debian blends/doc/en docs/talks/200811_dresden
CDD Subversion Commit
noreply at alioth.debian.org
Sun Nov 9 08:22:06 UTC 2008
Author: tille
Date: Sun Nov 9 08:22:05 2008
New Revision: 1233
Added:
blends/trunk/blends/debian/cdd-common.links
blends/trunk/blends/debian/cdd-dev.links
Modified:
blends/trunk/blends/debian/blends-common.install
blends/trunk/blends/debian/copyright
blends/trunk/blends/debian/rules
blends/trunk/blends/doc/en/05_inside.sgml
blends/trunk/blends/doc/en/06_technology.sgml
blends/trunk/blends/doc/en/07_starting.sgml
blends/trunk/blends/doc/en/08_websentinel.sgml
blends/trunk/blends/doc/en/09_todo.sgml
blends/trunk/blends/doc/en/A_devel.sgml
blends/trunk/blends/doc/en/B_quickintro.sgml
blends/trunk/blends/doc/en/C_bts.sgml
blends/trunk/docs/talks/200811_dresden/blends.tex
Log:
finish renaming docs, links for old cdd-* packages
Modified: blends/trunk/blends/debian/blends-common.install
==============================================================================
--- blends/trunk/blends/debian/blends-common.install (original)
+++ blends/trunk/blends/debian/blends-common.install Sun Nov 9 08:22:05 2008
@@ -1,7 +1,7 @@
-blends-user usr/sbin
-blends-role usr/sbin
-blends-update-menus usr/sbin
-blends-update-usermenus usr/sbin
-share usr
-etc/* etc
-blends-task-lister usr/share/blends
+blend-user usr/sbin
+blend-role usr/sbin
+blend-update-menus usr/sbin
+blend-update-usermenus usr/sbin
+share usr
+etc/* etc
+blend-task-lister usr/share/blends
Added: blends/trunk/blends/debian/cdd-common.links
==============================================================================
--- (empty file)
+++ blends/trunk/blends/debian/cdd-common.links Sun Nov 9 08:22:05 2008
@@ -0,0 +1,14 @@
+usr/share/blends/unixgroups/blend-actions usr/share/cdd/unixgroups/cdd-actions
+usr/share/blends/blend-actions usr/share/cdd/cdd-actions
+usr/share/blends/blend-update-menus usr/share/cdd/cdd-update-menus
+usr/share/blends/blend-utils usr/share/cdd/cdd-utils
+usr/share/blends/blend-task-lister usr/share/cdd/cdd-task-lister
+usr/share/man/man8/blend-actions.8.gz usr/share/man/man8/cdd-actions.8.gz
+usr/share/man/man8/blend-update-menus.8.gz usr/share/man/man8/cdd-update-menus.8.gz
+usr/share/man/man8/blend-utils.8.gz usr/share/man/man8/cdd-utils.8.gz
+usr/share/man/man8/blend-task-lister.8.gz usr/share/man/man8/cdd-task-lister.8.gz
+usr/sbin/blend-user usr/sbin/cdd-user
+usr/sbin/blend-role usr/sbin/cdd-role
+usr/sbin/blend-update-menus usr/sbin/cdd-update-menus
+usr/sbin/blend-update-usermenus usr/sbin/cdd-update-usermenus
+
Added: blends/trunk/blends/debian/cdd-dev.links
==============================================================================
--- (empty file)
+++ blends/trunk/blends/debian/cdd-dev.links Sun Nov 9 08:22:05 2008
@@ -0,0 +1,7 @@
+usr/share/blends/templates usr/share/cdd/templates
+usr/share/blends-dev/blend-gen-control usr/share/cdd-dev/cdd-gen-control
+usr/share/blends-dev/blend-get-names usr/share/cdd-dev/cdd-get-names
+usr/share/blends-dev/blend-install-helper usr/share/cdd-dev/cdd-install-helper
+usr/share/blends-dev/Makefile usr/share/cdd-dev/Makefile
+usr/share/blends-dev/rules usr/share/cdd-dev/rules
+usr/share/doc/blends-dev usr/share/doc/cdd-dev
Modified: blends/trunk/blends/debian/copyright
==============================================================================
--- blends/trunk/blends/debian/copyright (original)
+++ blends/trunk/blends/debian/copyright Sun Nov 9 08:22:05 2008
@@ -14,7 +14,7 @@
X-Comment: On Debian systems, the complete text of the GNU GPL version 2
can be found in: `/usr/share/common-licenses/GPL-2'
-Files: devtools/blends-gen-control
+Files: devtools/blend-gen-control
Copyright: © 2003-2007 Petter Reinholdtsen <pere at debian.org>
© 2007-2008 Andreas Tille <tille at debian.org>
License: GPL-2+
Modified: blends/trunk/blends/debian/rules
==============================================================================
--- blends/trunk/blends/debian/rules (original)
+++ blends/trunk/blends/debian/rules Sun Nov 9 08:22:05 2008
@@ -38,8 +38,9 @@
binary-indep: build install
dh_testdir
dh_testroot
- dh_installchangelogs
- dh_installdocs
+ # avoid installing doc directory for transitional packages
+ dh_installchangelogs -pblends-dev -pblends-common -pblends-doc
+ dh_installdocs -pblends-dev -pblends-common -pblends-doc
dh_installexamples
dh_installman
dh_lintian
Modified: blends/trunk/blends/doc/en/05_inside.sgml
==============================================================================
--- blends/trunk/blends/doc/en/05_inside.sgml (original)
+++ blends/trunk/blends/doc/en/05_inside.sgml Sun Nov 9 08:22:05 2008
@@ -22,11 +22,11 @@
<url id="http://www.libranet.com/" name="Libranet"> or
<url id="http://www.xandros.com/" name="Xandros">, there is no other
choice than forking because these companies normally add some stuff
-that is non-free. While Debian Integrated Solutions might be
-interesting in technical terms for those commercial distributions by
-making it easier to build a separate distribution, these non-free
-additions are not allowed to be integrated into Debian, and thus
-integration into Debian is impossible.
+that is non-free. While Debian Pure Blends might be interesting in
+technical terms for those commercial distributions by making it easier
+to build a separate distribution, these non-free additions are not
+allowed to be integrated into Debian, and thus integration into Debian
+is impossible.
</p>
</sect1>
@@ -34,13 +34,16 @@
<heading>Non-commercial forks</heading>
<p>
-Debian Integrated Solutions are a solution for derivatives from Debian
-that are as free as Debian but had certain reasons to fork. Most of
-these reasons existed in the past but have now vanished because Debian
-is becoming easier to adapt for special purposes. To increase this
-flexibility, the Debian Integrated Solutions approach was invented.
-Some examples of forks from Debian that are probably now able to
-integrate back into Debian are:
+As a completely free distribution Debian GNU/Linux is quite often a
+welcome starting point for derived distributions with a certain
+purpose that are as free as Debian but had certain reasons to fork.
+One main reason for a fork was that Debian was not flexible enough for
+certain purposes and some needed features had to be added. One reason
+for the Debian Pure Blends effort is to increase flexibility and to
+make the reason mentioned above void (if it is not yet void because of
+the general develoment of Debian). Some examples of forks from Debian
+that are probably now able to integrate back into Debian as a Debian
+Pure Blend are:
<taglist>
<tag><url id="http://www.skolelinux.org" name="SkoleLinux"></tag>
@@ -49,10 +52,10 @@
SkoleLinux people really doing a great job to enhance Debian
for their own purposes in the form of their work on
debian-installer, and culminated with the formal merging of
- the Debian Integrated Solution Debian Edu and SkoleLinux, so
- that they are now virtually equivalent. This is the
- recommended way for forked distributions, and the reasons for
- this recommendation are given below.
+ the Blend Debian Edu and SkoleLinux, so that they are now
+ virtually equivalent. This is the recommended way for derived
+ distributions, and the reasons for this recommendation are
+ given below.
</item>
<tag>DeMuDi</tag>
<item>The <url name="Agnula"
@@ -71,41 +74,42 @@
<tag>Organisational</tag>
<item>Because of the founded status of the project, an extra
distribution had to be developed. To accomplish this
- requirement, Debian Integrated Solutions plan to build common
- tools to facilitate building separate CDs with the contents
- of only a single distribution.</item>
+ requirement, Debian Pure Blends plan to build common tools to
+ facilitate building separate CDs with the contents of only a
+ single distribution.</item>
</taglist>
This shows that there is no longer a real need for a fork, and
- in fact, the organiser of the DeMuDi project is in contact to
- start bringing DeMuDi back into Debian. (That is why DeMuDi is
- mentioned in the list of Debian Integrated Solutions above.)
+ in fact, the organiser of the DeMuDi project was in contact to
+ start bringing DeMuDi back into Debian. That is why DeMuDi is
+ mentioned in the list of Debian Pure Blends above.
+ Unfortunately the effort to merge back has stalled but it
+ might be an interesting project to apply Blends techniques to
+ support multimedia experts who want to use Debian.
</item>
<tag>LinEx</tag>
- <item>LinEx is the very successful Distribution for schools in the
+ <item>LinEx is the very successful distribution for schools in the
Region Extremadura in Spain. The work of the LinEx people
- perhaps made Debian more popular than any other distribution.
- The project was founded by the local government of Extremadura,
- and each school in this region is running this distribution.
- While this is a great success, the further development of LinEx
- has to face the problems that will be explained below. So it
- might be worth considering following the path of SkoleLinux to
- integrate the needed stuff back into Debian. The LinEx people
- just did the first step, for instance, to try to get a free
- license for the very nice program
- <url id="http://www.squeak.org/" name="Squeak">.
+ perhaps made Debian more popular than any other distribution.
+ The project was founded by the local government of
+ Extremadura, and each school in this region is running this
+ distribution. While this is a great success, the further
+ development of LinEx has to face the problems that will be
+ explained below. Because the creators of LinEx are aware of
+ this fact they started joining the educational part of LinEx
+ with Debian Edu which in turn leaded to an even stronger
+ position of this Blend.
</item>
</taglist>
</p>
<p>
If developers of a non-commercial fork consider integrating back into
-Debian in the form of a Debian Integrated Solution, it might happen
-that their field is covered already by a Debian Integrated Solution.
-For instance, this would be the case for LinEx, which has exactly the
-same group of target users as Debian Edu. On the other hand, some
-special adaptations might be necessary to fit the requirements of the
-local educational system. The specific changes that might be
-necessary would be called <strong>flavours</strong> of a Debian
-Integrated Solution.
+Debian in the form of a Debian Pure Blend, it might happen that their
+field is covered already by an existing Blend. For instance, this
+would be the case for LinEx, which has the same group of target users
+as Debian Edu as explained above. On the other hand, some special
+adaptations might be necessary to fit the requirements of the local
+educational system. The specific changes that might be necessary
+would be called <strong>flavours</strong> of a Blend.
</p>
</sect1>
@@ -222,7 +226,7 @@
special fields of work, and so they try to make the best system for
their own needs. For children, they contribute to Debian Jr. or
Debian Edu. For their field of work, they contribute to the
-appropriate DIS: Debian Med, Debian Lex, and so forth.
+appropriate Blend: Debian Med, Debian Science, and so forth.
</p>
<p>
In contrast to employees of companies, every single Debian developer
@@ -256,7 +260,7 @@
sgml-always-quote-attributes:t
sgml-indent-step:2
sgml-indent-data:t
-sgml-parent-document:("../debian-dis.en.sgml" "book" "chapt")
+sgml-parent-document:("../debian-blends.en.sgml" "book" "chapt")
sgml-exposed-tags:nil
sgml-local-catalogs:nil
sgml-local-ecat-files:nil
Modified: blends/trunk/blends/doc/en/06_technology.sgml
==============================================================================
--- blends/trunk/blends/doc/en/06_technology.sgml (original)
+++ blends/trunk/blends/doc/en/06_technology.sgml Sun Nov 9 08:22:05 2008
@@ -8,42 +8,33 @@
<heading>Metapackage definition</heading>
<p>
-A metapackage, as used by DIShes, is a Debian package that contains:
+A metapackage, as used by Blends, 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 DIS in question.</p>
+ <item><p>Use "Depends" for packages that are definitely needed
+ for all basic stuff of the Blend in question.</p>
</item>
<tag>Recommends</tag>
- <item>The packages that are listed as "Recommends" in the
+ <item>The packages that are listed as "Recommends" in the
tasks file should be installed on the machine where the
metapackage is installed and which are needed to work
on a specific task.
</item>
<tag>Suggests</tag>
- <!-- [BA] Why would we suggest non-free? Doesn't policy allow a non-free
- package to specify "Enhances" to avoid this problem?
- [AT] I have to admit that "Enhances" is new to me. When
- reading policy I think this field is out of control of
- the metapackage developer because it has to be included
- by the package maintainer. I'm not really convinced that
- this is a good solution - but I would follow the suggestions
- of others in this issue.
- -->
- <item>Use "Suggests" for others of lesser importance that
+ <item>Use "Suggests" for others of lesser importance that
might be possibly useful, or non-free packages. When a
package is not available for the target distribution at
- metapackage build time the "Recommends" is turned into
- a "Suggests" to enable a flawless installation of the
+ metapackage build time the "Recommends" is turned into
+ a "Suggests" to enable a flawless installation of the
metapackage.
</item>
</taglist>
</item>
<item>Menu entries (recommended)
<list>
- <item>Place these in <file>/etc/dis/<var><dis></var>/menu/<var><pkg-name></var></file>
+ <item>Place these in <file>/etc/blends/<var><blend></var>/menu/<var><pkg-name></var></file>
<item>Maintain these via role based tools</item>
</list>
</item>
@@ -55,9 +46,9 @@
</item>
<item>Special metapackages:
<list>
- <item><package><var><dis></var>-tasks</package>:
+ <item><package><var><blend></var>-tasks</package>:
Contains information for <prgn>tasksel</prgn></item>
- <item><package><var><dis></var>-config</package>:
+ <item><package><var><blend></var>-config</package>:
Special configurations, basic stuff for user menus</item>
</list>
</item>
@@ -67,11 +58,12 @@
Metapackages are small packages with nearly no contents. The main
feature of this type of package is its dependencies on other
packages. The naming of metapackages follows the pattern
-<var><dis></var>-<var><task></var> where <var><dis></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
-Debian Integrated Solution, e.g. puzzle or bio.
+<var><blend></var>-<var><task></var>
+where <var><blend></var> stands for the short name of a Debian
+Pure Blend, 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 Blend,
+e.g. puzzle or bio.
</p>
<p>
Examples:
@@ -148,22 +140,22 @@
<p>
A "traditional" weakness of Free Software projects is missing
-documentation. To fix this, Debian Integrated Solutions try to provide
+documentation. To fix this, Debian Pure Blends try to provide
relevant documentation to help users to solve their problems. This
can be done by building <package>*-doc</package> packages of existing
-documentation, and by writing extra documentation, like manpages, etc. By
-supplying documentation, Debian Integrated Solutions fulfil
-their role in addressing the needs of specialised users, who have a great
-need for good documentation in their native language.
+documentation, and by writing extra documentation, like manpages, etc.
+By supplying documentation, Debian Pure Blends fulfil their role in
+addressing the needs of specialised users, who have a great need for
+good documentation in their native language.
</p>
<p>
Thus, translation is a very important thing to make programs more
-useful for the target user group. Debian has established a <url
-id="http://ddtp.debian.net/" name="Debian Description Translation
-Project">, which has the goal to translate package descriptions. There
-is a good chance this system could also be used for other types of
-documentation, which might be a great help for Debian Integrated
-Solutions.
+useful for the target user group. Debian has established
+a <url id="http://ddtp.debian.net/" name="Debian Description
+Translation Project">, which has the goal to translate package
+descriptions. There is a good chance this system could also be used
+for other types of documentation, which might be a great help for
+Debian Pure Blends.
</p>
</sect1>
@@ -197,17 +189,15 @@
The program <prgn>apt-cache</prgn> is useful to search for
relevant keywords in package descriptions. With it, you could search
for a certain keyword connected to your topic (for instance
- "<tt>med</tt>") and combine it reasonably with <prgn>grep</prgn>:
+ "<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-bio-dev - Debian Med micro-biology development packages
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>
@@ -227,10 +217,6 @@
Depends: paul, ctsim, ctn, minc-tools, medcon, xmedcon, med-common
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
-
Package: med-bio
Depends: bioperl, blast2, bugsx, fastdnaml, fastlink, garlic...
Description: Debian Med micro-biology packages
@@ -239,10 +225,6 @@
Depends: adduser, debconf (>= 0.5), menu
Description: Debian Med Project common package
-Package: med-common-dev
-Depends: debconf (>= 0.5)
-Description: Debian Med Project common files for developing ...
-
Package: med-tools
Depends: mencal, med-common
Description: Debian Med several tools
@@ -326,8 +308,8 @@
The short conclusion here is: <strong>There are no sophisticated tools
that might be helpful to handle metapackages as they are used in
-Debian Integrated Solutions - just some hacks using the powerful tools
-inside Debian.</strong>
+Debian Pure Blends - just some hacks using the powerful tools inside
+Debian.</strong>
</p>
</sect1>
@@ -344,10 +326,10 @@
<tag><prgn>tasksel</prgn></tag>
<item>
The Debian task installer <prgn>Tasksel</prgn> is the first
- 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.
+ 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 Pure Blend. This is currently
+ the case for Debian Jr.
<example>
Debian Task Installer v1.43 - (c) 1999-2003 SPI and others
@@ -377,22 +359,21 @@
</example>
Unfortunately, there are some issues that prevent further Debian
- Integrated Solutions from being included in
- the <prgn>tasksel</prgn> list, because the dependencies of this
- task can affect what appears on the first installation CD. This
- problem would be even greater if all Debian Integrated Solutions
- were added, and so a different solution has to be found
- here. (See <url id="http://bugs.debian.org/186085"
+ Pure Blends from being included in the <prgn>tasksel</prgn> list,
+ because the dependencies of this task can affect what appears on
+ the first installation CD. This problem would be even greater if
+ all Debian Pure Blends were added, and so a different solution has
+ to be found here. (See <url id="http://bugs.debian.org/186085"
name="#186085">.) In principle, <prgn>tasksel</prgn> is a good
- tool for easy installation of Debian Integrated Solutions.
+ tool for easy installation of Blends.
</item>
<tag><prgn>aptitude</prgn></tag>
<item>
- This is a better replacement for <prgn>dselect</prgn>, and has some
- useful support for searching for and grouping of packages. While
- this is not bad, it was not intended for the purpose of handling
- Debian Integrated Solutions, and thus there could be some better support
- to handle metapackages more cleverly.
+ This is a better replacement for <prgn>dselect</prgn>, and has
+ some useful support for searching for and grouping of packages.
+ While this is not bad, it was not intended for the purpose of
+ handling Debian Pure Blends, and thus there could be some better
+ support to handle metapackages more cleverly.
</item>
</taglist>
Short conclusion: <strong>There is a good chance metapackages could be
@@ -413,20 +394,20 @@
<tag><prgn>gnome-apt</prgn></tag>
<item>This is the native GNOME flavour of graphical user interfaces
to apt. It has a nice <tt>Search</tt> feature that can be
- found in the <tt>Package</tt> menu section. If for
- instance the packages of the Debian Jr. project come into the
- focus of interest a search for "<tt>junior-*</tt>" will show
- up all related packages including their descriptions. This
- will give a reasonable overview about metapackages of the
- project.
+ found in the <tt>Package</tt> menu section. If for instance
+ the packages of the Debian Jr. project come into the focus of
+ interest a search for "<tt>junior-*</tt>" will show
+ up all related packages including their descriptions. This
+ will give a reasonable overview about metapackages of the
+ project.
</item>
<tag><prgn>synaptic</prgn></tag>
<item>Even more sophisticated and perhaps the best choice for users
- of Debian Integrated Solutions. <prgn>Synaptic</prgn> has a
- nice filter feature, which makes it a great tool here.
- Moreover <prgn>synaptic</prgn> is currently the only user
- interface that supports Debian Package Tags (see <ref
- id="debtags">).
+ of Debian Pure Blends. <prgn>Synaptic</prgn> has a nice
+ filter feature, which makes it a great tool here.
+ Moreover <prgn>synaptic</prgn> is currently the only user
+ interface that supports Debian Package Tags
+ (see <ref id="debtags">).
</item>
<tag><prgn>kpackage</prgn></tag>
<item>This is the user interface of choice for KDE lovers.
@@ -436,7 +417,7 @@
</taglist>
Short conclusion: <strong>As well as the text based user interfaces
these tools are quite usable but need enhancements to be regarded as
-powerful tools for Debian Integrated Solutions.</strong>
+powerful tools for Debian Pure Blends.</strong>
</p>
</sect1>
@@ -445,6 +426,72 @@
<p>
<taglist>
+ <tag>Tasks pages</tag>
+ <item><p>The tasks pages probably provide the best overview about
+ the actual work which is done in a Debian Pure Blend. These
+ pages are automatically generated by reading the tasks files
+ (see <ref id="debian_control">) and verifying the existence
+ of the packages that are mentioned as dependencies. On the
+ resulting web page the packages are listed with some meta
+ information and the description of the package. As user
+ oriented pages they are translated into more than 10
+ languages while translated means, the navigation text of the
+ page generating code is using <prgn>gettext</prgn> which
+ enables translation (the work is not yet completely done for
+ all languages) but even more importantly the descriptions of
+ the packages are translated as well by using the information
+ from
+ <url id="http://ddtp.debian.net/" name="Debian Description
+ Translation Project" >.
+ </p>
+ <p>These tasks pages are available via
+ <example>
+ http://cdd.alioth.debian.org/BLEND/tasks
+ </example>
+ where <tt>BLEND</tt> has to be replaced by the name of the
+ Blend. Currently these pages are available for the Blends:
+ <example>
+ edu, gis, junior, science, debichem
+ </example>
+ The tasks pages are available for Debian Med as well but for
+ historical reasons the URL for these pages is
+ <example>
+ http://debian-med.alioth.debian.org/tasks
+ </example>
+ In short: If you want to know more about a specific Blend
+ go to its task page and have a look what is listed there.
+ </p>
+ </item>
+ <tag>Bugs pages</tag>
+ <item><p>The more developer oriented bugs pages try to match the
+ scope of the tasks pages mentioned above but there is no
+ description of the packages given but rather the bugs that
+ are reported in the Debian Bug Tracking System (BTS) are
+ listed there. This is a quite valuable source of information
+ if somebody is interested in increasing the quality of a
+ Blend: Fixing bugs is always welcome and listing all relevant
+ bugs at a single place is a nice way to detect problems
+ quickly.
+ </p>
+ <p>These bugs pages are available via
+ <example>
+ http://cdd.alioth.debian.org/BLEND/bugs
+ </example>
+ where <tt>BLEND</tt> has to be replaced by the name of the
+ Blend. Currently these pages are available for the Blends:
+ <example>
+ edu, gis, junior, science, debichem
+ </example>
+ The bugs pages are available for Debian Med as well but for
+ historical reasons the URL for these pages is
+ <example>
+ http://debian-med.alioth.debian.org/bugs
+ </example>
+ In short: If you want to help enhancing the quality of a
+ specific Blend go to its bug page and start working on the
+ bugs listed there.
+ </p>
+ </item>
<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
@@ -462,34 +509,38 @@
<tag><url id="http://qa.debian.org/developer.php" name="Package Tracking System"></tag>
<item><p>
The Package Tracking System is a really great tool that
- provides essential information about packages. Regarding
- Debian Integrated Solutions it can help if you know the
- Debian user name of the developer who is responsible for the
- metapackages:
+ provides essential information about packages. Most Debian
+ Pure Blends are using a mailing list address as Maintainer of
+ their key packages which includes the metapackages. This so
+ called team maintenance of packages is on one hand very handy
+ from a developers point of view on the other hand it enables
+ using the Package Tracking System to get a quick overview:
<taglist>
<tag>Debian Jr:</tag>
<item>
- <url id="http://qa.debian.org/developer.php?login=synrg">
+ <url id="http://qa.debian.org/developer.php?login=debian-jr@lists.debian.org">
</item>
<tag>Debian Med:</tag>
<item>
- <url id="http://qa.debian.org/developer.php?login=tille">
+ <url id="http://qa.debian.org/developer.php?login=debian-med-packaging@lists.alioth.debian.org">
</item>
<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>
- <item>
- <url id="http://qa.debian.org/developer.php?login=mako">
+ <url id="http://qa.debian.org/developer.php?login=debian-edu@lists.debian.org">
</item>
- <tag>Debian Lex:</tag>
+ <tag>Debian Science:</tag>
<item>
- <url id="http://qa.debian.org/developer.php?login=terminus">
+ <url id="http://qa.debian.org/developer.php?login=debian-science-maintainers@lists.alioth.debian.org">
</item>
--->
</taglist>
+ Hint: If you append the option <prgn>&ordering=3</prgn> you
+ might get some sectioning of this page according to the
+ metapackage categories. This result is approached by a tool
+ which subscribes all dependent packages to the group
+ maintenance address and adds a section according to a
+ metapackage name.
+ </p>
+ <p>
The other way to use the Package Tracking System is to search
for packages starting with a certain letter:
<taglist>
@@ -505,21 +556,20 @@
But the list that is obtained by this method is much larger
than it would be useful for a good overview.
</p><p>
- So the conclusion is - we just need better support here for
- Debian Integrated Solutions.
</p>
<tag><prgn>list-junior.sh</prgn></tag>
<item>The package <package>junior-doc</package> contains a script
<file>/usr/share/doc/junior-doc/examples/scripts/list-junior.sh</file>
- that checks for the installed packages of a Debian Integrated
- Solution and builds a simple web page describing these
- packages. (The BTS contains a patch to let this script work
- also for other Debian Integrated Solutions.)
+ that checks for the installed packages of a Blend and builds
+ a simple web page describing these packages. (The BTS
+ contains a patch to let this script work also for other
+ Blends.)
</item>
</taglist>
-Short conclusion: <strong>Some very basic things can be done with the
-web interfaces described above but techniques have to be developed to
-provide useful information about each Debian Integrated Solution.</strong>
+Short conclusion: <strong>The Debian Pure Blends provide some nice web
+ tools for a whole set of packages for a certain working field that
+ provide a better overview than the usual Debian tools that are
+ basically dealing with single packages..</strong>
</p>
</sect1>
@@ -546,9 +596,9 @@
</p>
<p>
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.
+Pure Blend 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>
<p>
Tools that grep the apt cache directly for metapackages have to be
@@ -572,14 +622,13 @@
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 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.
+to be implemented for certain groups of users of one Blend, which are
+called "roles". There are several techniques available to manage user
+roles. Currently in the field of Debian Pure Blends a UNIX group
+based role system is implemented. This means, that a user who belongs
+to a certain group of a Blend 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
@@ -590,8 +639,8 @@
impact on the general use of the system. The benefit of using unix
groups is that there is a defined set of tools provided to handle user
groups. This makes life much easier; there is no
-<em>practical</em> limit to the number of groups to which a user
-may belong for the existing Debian Integrated Solutions at this time.
+<em>practical</em> limit to the number of groups to which a user may
+belong for the existing Debian Pure Blends at this time.
</p>
<p>
In the long run, this role system might even be enhanced to certain
@@ -600,8 +649,8 @@
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.
+level maintenance is not only a topic for Debian Pure Blends but might
+be interesting for Debian in general.
</p>
<p>
Another point that speaks against using UNIX groups for role
@@ -626,16 +675,16 @@
installation. To enable compliance with the <em>role</em> based menu
approach it is necessary to rebuild the user menu after each package
installation or after adding new users to the intended role. This can
-be done by using the <manref name="dis-update-menus" section="8"> (see
-<ref id="dis-update-menus">) script from
-<package>dis-common</package>. It has to be said that using
-<prgn>dis-update-menus</prgn> is not enough to change the menu of a
+be done by using the <manref name="blend-update-menus" section="8"> (see
+<ref id="blend-update-menus">) script from
+<package>blends-common</package>. It has to be said that using
+<prgn>blend-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
-Debian Integrated Solution is necessary if this is not done by the
+<prgn>update-menu</prgn> script for every single user of a Blend 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/dis/<var><dis></var>/<var><dis></var>.conf</file> contains the
+done if the configuration file of a Debian Pure Blend
+<file>/etc/blends/<var><blend></var>/<var><blend></var>.conf</file> contains the
line
<example>
UPDATEUSERMENU=yes
@@ -643,22 +692,23 @@
</p>
<p>
-It is strongly suggested to use the package <package>dis-dev</package>
-to build metapackages of a Debian Integrated Solution that will move
-all necessary files right into place if there exists a
+It is strongly suggested to use the
+package <package>blends-dev</package> to build metapackages of a
+Debian Pure Blend that will move all necessary files right into place
+if there exists a
<file>menu</file> directory with the menu entries. Note, that the users
<file>${HOME}/.menu</file> directory remains untouched.
</p>
</sect2>
<sect2 id="user-debconf">
- <heading>Managing Debian Integrated Solution users with <prgn>debconf</prgn></heading>
+ <heading>Managing Debian Pure Blend users with <prgn>debconf</prgn></heading>
<p>
-Using <package>dis-dev</package> it is very easy to build a
-<var>dis</var><package>-config</package> package that contains
+Using <package>blends-dev</package> it is very easy to build a
+<var>blend</var><package>-config</package> package that contains
<prgn>debconf</prgn> scripts to configure system users who should
-belong to the group of users of the Debian Integrated Solution <var>dis</var>.
+belong to the group of users of the Debian Pure Blend <var>blend</var>.
For example see the <package>med-common</package> package.
<example>
@@ -699,27 +749,27 @@
<p>
Building a metapackage is more or less equal for each meta
package. This was the reason to build a common source package
-<package>dis</package> that builds into two binary packages
+<package>blend</package> that builds into two binary packages
<taglist>
- <tag><package>dis-dev</package></tag>
+ <tag><package>blends-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
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
- id="dis-dev">.</p>
+ id="blends-dev">.</p>
</item>
- <tag><package>dis-common</package></tag>
+ <tag><package>blends-common</package></tag>
<item><p>This package provides some files that are common to meta
- packages of Common Debian Distributions especially those
- that were built using the tools of the package
- <package>dis-dev</package>. It introduces a method to handle
+ packages of Debian Pure Blends especially those that were
+ built using the tools of the package
+ <package>blends-dev</package>. It introduces a method to handle
system users in a group named according to the name of the
- Debian Integrated Solution. The user menu approach is
- explained in detail in <ref id="userroles">.</p>
+ Blend. The user menu approach is explained in detail
+ in <ref id="userroles">.</p>
<p>This package is described in detail in appendix <ref
- id="dis-common">.</p>
+ id="blends-common">.</p>
</item>
</taglist>
The usage of the tools that are contained in these packages are
@@ -730,19 +780,19 @@
<heading>Other interesting tools</heading>
<sect1 id="simple-cdd">
- <heading>Simple-DIS</heading>
+ <heading>Simple-CDD</heading>
<p>
The tool <prgn>simple-cdd</prgn> is a limited though relatively easy
tool to create a customized debian-installer CD.
</p><p>
-It includes simple mechanisms to create "profiles" that define common
+It includes simple mechanisms to create "profiles" that define common
system configurations, which can be selected during system
installation. <prgn>Simple-cdd</prgn> also makes it easy to build CDs
with language and country settings pre-configured, or to use a 2.6
kernel by default.
</p><p>
-This can be used to create a crude "Debian Integrated Solution" using
+This can be used to create a crude "Debian Pure Blend" using
packages from debian, with pre-configuration of packages that use
<prgn>debconf</prgn>. Custom configuration scripts can be specified
to handle packages that don't support <prgn>debconf</prgn>
@@ -772,7 +822,7 @@
sgml-always-quote-attributes:t
sgml-indent-step:2
sgml-indent-data:t
-sgml-parent-document:("../debian-dis.en.sgml" "book" "chapt")
+sgml-parent-document:("../debian-blends.en.sgml" "book" "chapt")
sgml-exposed-tags:nil
sgml-local-catalogs:nil
sgml-local-ecat-files:nil
Modified: blends/trunk/blends/doc/en/07_starting.sgml
==============================================================================
--- blends/trunk/blends/doc/en/07_starting.sgml (original)
+++ blends/trunk/blends/doc/en/07_starting.sgml Sun Nov 9 08:22:05 2008
@@ -1,46 +1,41 @@
<chapt id="starting">
- <heading>How to start a Debian Integrated Solution</heading>
+ <heading>How to start a Debian Pure Blend</heading>
<p>
-This chapter more or less covers the text of the <url
-id="http://packages.debian.org/unstable/doc/subproject-howto.html"
-name="Debian Subproject HOWTO">, which was written by Ben Armstrong
-<email>synrg at debian.org</email>. Ben has agreed that his text should
-be included here, and the <package>subproject-howto</package> will be
-orphaned once the current document is ready for packaging.
+This chapter is based on the Debian Subproject HOWTO, which was
+written by Ben Armstrong <email>synrg at debian.org</email>.
</p>
<sect id="planning">
- <heading>Planning to form a Debian Integrated Solution</heading>
+ <heading>Planning to form a Debian Pure Blend</heading>
<p>
- In this section, issues to think about before starting a Debian
- Integrated Solution will be discussed. It is important to have a
- clear idea where to head and how to get there before launching into
- this adventure.
+ In this section, issues to think about before starting a Debian Pure
+ Blend will be discussed. It is important to have a clear idea where
+ to head and how to get there before launching into this adventure.
</p>
<sect1 id="leadership">
<heading>Leadership</heading>
<p>
- The existing Debian Integrated Solutions have clearly shown
- that they depend on a person who keeps things running. If anybody
- wants to start a project at first, he has to answer the question:
- <em>"Am I the right person for the job?"</em> Surely this is a
- question that may be faced with some amount of uncertainty. The
- way Debian Integrated Solutions started in the past
- was for the person with the idea for the project to just start
- doing the work. After some time using this approach, it became clear that
- if the project lacked a person to take leadership, the project would become
- stale. So the initiator has to answer the question clearly, whether
- or not he is able to continue in the <em>job</em> of leader, considering
- the amount of time he will have to spend, and the technical and social
+ The existing Debian Pure Blends have clearly shown that they depend
+ on a person who keeps things running. If anybody wants to start a
+ project at first, he has to answer the question:
+ <em>"Am I the right person for the job?"</em> Surely this is a
+ question that may be faced with some amount of uncertainty. The way
+ Debian Pure Blends started in the past was for the person with the
+ idea for the project to just start doing the work. After some time
+ using this approach, it became clear that if the project lacked a
+ person to take leadership, the project would become stale. So the
+ initiator has to answer the question clearly, whether or not he is
+ able to continue in the <em>job</em> of leader, considering the
+ amount of time he will have to spend, and the technical and social
skills which are needed.
</p>
</sect1>
<sect1 id="defining_scope">
- <heading>Defining the subproject scope</heading>
+ <heading>Defining the scope of the Blend</heading>
<p>
It is as important to decide what your group is not going to do as
it is what it is going to do. A clear borderline is essential for
@@ -55,16 +50,16 @@
shared, the amount of work for each project can be reduced.
</p>
<p>
- Checking for cooperation with other Debian Integrated Solutions is
- always a good idea. In technical terms, this is obvious, but
- sometimes there are possibilities to share efforts when the goals
- of two projects have parts in common.
+ Checking for cooperation with other Debian Pure Blends is always a
+ good idea. In technical terms, this is obvious, but sometimes there
+ are possibilities to share efforts when the goals of two projects
+ have parts in common.
</p>
<p>
- The one who decides to start a Debian Integrated Solution takes on a
+ The one who decides to start a Debian Pure Blend takes on a
responsibility for this project. It has to be for the good of
- Debian as a whole, and should bring an extra reputation to our common
- goal to build the best operating system.
+ Debian as a whole, and should bring an extra reputation to our
+ common goal to build the best operating system.
</p>
</sect1>
@@ -158,24 +153,31 @@
<sect1>
<heading>Web space</heading>
<p>
- A fairly important way to let people know what your Debian
- Integrated Solution is about is certainly a web page. While there
- are a number of ways to go about this, the simplest is to put them
- at the developer home page at <url id="http://people.debian.org"> if
- an official Debian developer is starting the project.
+ A simple possibility, and one which is fairly attractive because it
+ facilitates collaborative web site creation and maintenance, is to
+ put a page on the <url name="Wiki" id="http://wiki.debian.org">.
+ There is a
+ special <url id="http://wiki.debian.org/index.cgi?DebianPureBlends"
+ name="Wiki page for Debian Pure Blends">.
+ </p>
+ <p>
+ A good place to put static web pages or even PHP code is the common
+ place on Alioth for all
+ Blends: <url id="http://cdd.alioth.debian.org">. There is a
+ subdirectory for each Blend and it is very easy to create a simple
+ index page there which points to the automatically generated web
+ pages which are mentioned in <ref id="web_if">. Following this
+ strategy is quite cheap and has a big effect when using the tools
+ provided by the Debian Pure Blends effort.
</p>
<p>
- Another possibility, and one which is fairly attractive because
- it facilitates collaborative web site creation and maintenance,
- is to put a page on the <url name="Wiki" id="http://wiki.debian.org">. There
- is a special <url id="http://wiki.debian.org/index.cgi?CustomDebian"
- name="Wiki page for Debian Integrated Solutions">.
- </p>
- <p>
- A third, and more recent possibility is to start a project at
+ Sooner or later a Debian Pure Blend will establish an own project at
<url id="http://alioth.debian.org" name="alioth.debian.org">, since
- hosting Debian development projects is the whole reason for this
- site.
+ this enables many features for group maintaining packages, create
+ mailing lists for different purposes, maintain a version control
+ system like SVN or Git etc. The Alioth project enables to provide
+ web sites as well and the Debian Med project is using this since a
+ long time.
</p>
<p>
Finally, the best way is to have a page
@@ -183,13 +185,13 @@
straightforward as any of the other options, this approach has its
advantages. First, the site is mirrored everywhere. Second, the
Debian web site translators translate pages into many different
- languages, reaching new potential audiences for your Debian
- Integrated Solution, and improving communication with other members
- of your project and interested parties for whom English is not their
- most comfortable language. Third, a number of templates are
- available to make your site more integrated with the main web site,
- and to assist with incorporating some dynamic content into your
- site. Before you join the Debian Web team you
+ languages, reaching new potential audiences for your Debian Pure
+ Blend, and improving communication with other members of your
+ project and interested parties for whom English is not their most
+ comfortable language. Third, a number of templates are available to
+ make your site more integrated with the main web site, and to assist
+ with incorporating some dynamic content into your site. Before you
+ join the Debian Web team you
should <url id="http://www.debian.org/devel/website" name="learn
more about building Debian web pages">.
</p>
@@ -207,8 +209,8 @@
On <url id="http://alioth.debian.org/" name="alioth.debian.org"> a
<url id="http://gforge.org/" name="Gforge">-site is running to host
all Debian related project work. Creating a project on Alioth is a
- good idea to start teamwork on the code a certain Debian Integrated
- Solution is releasing.
+ good idea to start teamwork on the code a Debian Pure Blend is
+ releasing.
</p>
</sect1>
@@ -217,8 +219,8 @@
<p>
Once there is a list, or at least enough preliminary discussion on
debian-devel to get started, and there is some information about the
- newly planned Debian Integrated Solution available on the web,
- it is time to send a formal announcement to
+ newly planned Debian Pure Blend available on the web, it is time to
+ send a formal announcement to
<email>debian-devel-announce at lists.debian.org</email>. The
announcement should include references to past discussions, any web
pages and code which might already exist, and summarise in a well thought
@@ -259,10 +261,10 @@
While there are a variety of different kinds of work to be done in
Debian, and not all of them follow this pattern, this document
describes one particular kind of project. Our discussion about
- Debian Integrated Solutions concerns sub-setting Debian. A
- sub-setting project aims to identify, expand, integrate, enhance, and
- maintain a collection of packages suitable for a particular purpose
- by a particular kind of user.
+ Debian Pure Blends concerns sub-setting Debian. A sub-setting
+ project aims to identify, expand, integrate, enhance, and maintain a
+ collection of packages suitable for a particular purpose by a
+ particular kind of user.
</p>
<p>
Now, strictly speaking, a subset of packages could be more general
@@ -329,9 +331,8 @@
</p>
<p>
Section <ref id="text_ui"> mentions <prgn>tasksel</prgn> as a tool
- to select a Debian Integrated Solution, and explains why
- it is currently not possible to get a Debian Integrated Solution
- included into the task selection list.
+ to select a Debian Pure Blend, and explains why it is currently not
+ possible to get a Blend included into the task selection list.
</p>
</sect1>
@@ -345,7 +346,7 @@
<p>
Beyond the release announcement for Debian itself, it is necessary
to put some thought and work into a release announcement for the
- first release of a Debian Integrated Solution. This will not only
+ first release of a Debian Pure Blend. This will not only
be directed at the Debian developer community, but also at the users.
This will include potential new Debian users abroad, who may not be
on a Debian mailing list. Here, the same principle applies as for
@@ -355,12 +356,12 @@
</sect1>
<sect1 id="users">
- <heading>Users of a Debian Integrated Solution</heading>
+ <heading>Users of a Debian Pure Blend</heading>
<p>
By this time, people have newly installed Debian along with the
- material in the Debian Integrated Solution, or have installed the meta
- packages on their existing Debian systems. Now comes the fun part,
- building relationships with the user community.
+ material in the Blend, or have installed the metapackages on their
+ existing Debian systems. Now comes the fun part, building
+ relationships with the user community.
</p>
<sect2 id="user_support">
@@ -424,7 +425,7 @@
sgml-always-quote-attributes:t
sgml-indent-step:2
sgml-indent-data:t
-sgml-parent-document:("../debian-dis.en.sgml" "book" "chapt")
+sgml-parent-document:("../debian-blends.en.sgml" "book" "chapt")
sgml-exposed-tags:nil
sgml-local-catalogs:nil
sgml-local-ecat-files:nil
Modified: blends/trunk/blends/doc/en/08_websentinel.sgml
==============================================================================
--- blends/trunk/blends/doc/en/08_websentinel.sgml (original)
+++ blends/trunk/blends/doc/en/08_websentinel.sgml Sun Nov 9 08:22:05 2008
@@ -11,13 +11,13 @@
like that just follow the instructions below.
</p>
<p>
-If a Debian Integrated Solution should be presented one of the first
-questions is, what packages are available. The next question might be
-which packages are on the todo list for inclusion in Debian to make
-Debian even more attractive for people the DIS is targeting at. Both
+If a Debian Pure Blend should be presented one of the first questions
+is, what packages are available. The next question might be which
+packages are on the todo list for inclusion in Debian to make Debian
+even more attractive for people the Blend is targeting at. Both
questions can be answered if you point people to the dynamically
created tasks page. The page is rebuild daily to stay up to date
-according to recent developments of the DIS. The build process works
+according to recent developments of the Blend. The build process works
as follows:
<list>
<item>Read dependency information of the <file>tasks</file> files.</item>
@@ -32,12 +32,12 @@
<p>
The rationale behind this is to provide as much as possible
information about packages that might be interesting for the target
-user of the DIS. Moreover the page can provide useful information for
+user of the Blend. Moreover the page can provide useful information for
developers about things that might be a useful help for the project to
work down the todo list and build Debian packages for software that is
not yet included in Debian. To get the todo list builded it is
necessary to add some additional information to the task files which
-are the main database of information for the DIS. The information is
+are the main database of information for the Blend. The information is
following the RFC822 syntax as all Debian control files do and is
kept quite simple:
<taglist>
@@ -89,7 +89,7 @@
yet have an official Debian maintainer status and thus are not
able to upload packages to the Debian mirror. The packages at
mentors are waiting for sponsoring of an official Debian
- maintainer and if such a package shows up in the DIS tasks list
+ maintainer and if such a package shows up in the Blend tasks list
it might speed up the inclusion into official Debian
distribution.
</item>
@@ -113,9 +113,9 @@
Translation Project"> (see <ref id="documentation">) provides users of
non English languages with information about Debian packages. The
sense of supporting especially the translations of descriptions which
-are in the focus of a DIS is to make the DIS even more usable for our
+are in the focus of a Blend is to make the Blend even more usable for our
target users. Moreover people interested in the special field of the
-DIS are most probably able to provide good translations if it comes to
+Blend are most probably able to provide good translations if it comes to
texts that are specific to their field of knowledge. Thus there is a
web page automatically created that parses the tasks packages for
package names and verifies the translation status of the package
@@ -132,7 +132,7 @@
<sect id="bugs">
<heading>Bugs overview</heading>
<p>
-The goal of a DIS is to support their user as best as possible. So a
+The goal of a Blend is to support their user as best as possible. So a
feature to have a quick overview about all packages in our focus might
be helpful. This is solved by the bugs overview page. To create this
page the <file>tasks</file> files are parsed for the listed
@@ -140,7 +140,7 @@
known bugs of these packages. All bugs are listed and marked with
different colours according to their severity. So the developers can
easily check this page in case they plan to fix some bugs that are
-relevant for the DIS.
+relevant for the Blend.
</p>
</sect>
@@ -148,7 +148,7 @@
<heading>SVN overview</heading>
<p>
This page gives a recent overview about the current development
-activities of the DIS developers.
+activities of the Blend developers.
</p>
</sect>
@@ -160,7 +160,7 @@
status o f Debian packages. If a package features a
valid <file>debian/watch</file> the tool <prgn>uscan</prgn> is able to
verify the upstream source location for newer versions. The QA report
-page reports issues about the packages that are relevant for a DIS.
+page reports issues about the packages that are relevant for a Blend.
</p>
</sect>
@@ -177,7 +177,7 @@
sgml-always-quote-attributes:t
sgml-indent-step:2
sgml-indent-data:t
-sgml-parent-document:("../debian-dis.en.sgml" "book" "chapt")
+sgml-parent-document:("../debian-blends.en.sgml" "book" "chapt")
sgml-exposed-tags:nil
sgml-local-catalogs:nil
sgml-local-ecat-files:nil
Modified: blends/trunk/blends/doc/en/09_todo.sgml
==============================================================================
--- blends/trunk/blends/doc/en/09_todo.sgml (original)
+++ blends/trunk/blends/doc/en/09_todo.sgml Sun Nov 9 08:22:05 2008
@@ -5,67 +5,67 @@
<heading>Establishing and using communication platforms</heading>
<p>
-Each Debian Integrated Solution has an own mailing list for discussion
-of specific development issues. Because there are several common
-issues between all Debian Integrated Solutions also a common mailing
-list was created. People who are interested in working on common
-issues like building metapackages, technical issues of menu systems
-or how to create CDs for Debian Integrated Solutions could <url
-id="http://lists.debian.org/debian-custom/" name="subscribe to this
-list or read the list archive">.
+Each Debian Pure Blend has an own mailing list for discussion of
+specific development issues. Because there are several common issues
+between all Blends also a common mailing list was created. People who
+are interested in working on common issues like building metapackages,
+technical issues of menu systems or how to create CDs for Blends
+could <url id="http://lists.debian.org/debian-custom/" name="subscribe
+to this list or read the list archive">.
</p>
<p>
-Moreover the project <url
-id="http://alioth.debian.org/projects/cdd/" name="dis"> on Alioth was
-started. The <url id="http://svn.debian.org/viewcvs/cdd/"
-name="subversion repository"> can be browsed or checked out by
-by
+Moreover the project <url id="http://alioth.debian.org/projects/cdd/"
+name="CDD"> on Alioth was started. After the rename from CDD (Custom
+Debian Distributions) to Debian Pure Blends the Alioth project has to
+be removed to finalise the rename - but this is not yet
+done. The <url id="http://svn.debian.org/viewcvs/cdd/"
+name="subversion repository"> can be browsed or checked out by by
<example>
- svn checkout svn://svn.debian.org/svn/cdd/cdd/trunk
+ svn checkout svn://svn.debian.org/svn/cdd/blends/trunk
</example>
for anonymous users. Developers should check out via
<example>
- svn checkout svn+ssh://<var>username</var>@svn.debian.org/svn/cdd/cdd/trunk dis
+ svn checkout svn+ssh://<var>username</var>@svn.debian.org/svn/cdd/blends/trunk blends
</example>
The current layout for the repository is as follows:
<example>
- cdd -+- cdd -+- branches -+- cdd -+- 0.3.x
- | |
- | +- tags -----+- cdd -+- 0.3 [older versions of cdd tools]
- | | | +- 0.3.1
- | | | ...
- | | | +- <var><latest></var>
- | | |
- | | +- doc -+- 0.1 [older versions of this doc]
- | | +- 0.2
- | | +- 0.3
- | | [Since 0.4.1 the doc is in cdd directory]
- | |
- | +- trunk ----dis [code in development for dis source package]
- | |
- | +-- doc [this document = dis-doc package]
+ cdd -+- blends -+- branches -+- cdd -+- 0.3.x
+ | |
+ | +- tags -----+- cdd -+- 0.3 [older versions of cdd tools]
+ | | | +- 0.3.1
+ | | | ...
+ | | | +- <var><latest></var>
+ | | |
+ | | +- doc -+- 0.1 [older versions of this doc]
+ | | +- 0.2
+ | | +- 0.3
+ | | [Since 0.4.1 the doc is in blends directory]
+ | |
+ | +- trunk ----blends [code in development for blends source package]
+ | |
+ | +-- doc [this document = blends-doc package]
|
+- projects -+--- med ---+- branches
| |
| +- tags
| |
- | +- trunk [development version of Debian-Med]
+ | +- trunk [development version of Debian Med]
|
+- science -+- branches
| |
| +- tags
| |
- | +- trunk [development version of Debian-Science]
+ | +- trunk [development version of Debian Science]
|
+- ...
|
...
</example>
-There is a <url
-id="http://lists.alioth.debian.org/mailman/listinfo/cdd-commits"
-name="mailing list"> with subversion changes and a <url
-id="http://cia.navi.cx/stats/project/debian-custom" name="CIA system">
-for tracking changes in the Debian Integrated Solutions projects in
+There is
+a <url id="http://lists.alioth.debian.org/mailman/listinfo/cdd-commits"
+name="mailing list"> with subversion changes and
+a <url id="http://cia.navi.cx/stats/project/debian-custom" name="CIA
+system"> for tracking changes in the Debian Pure Blends projects in
real-time.
</p>
</sect>
@@ -76,57 +76,53 @@
<p>
If a user installs Debian via official install CDs the first chance to
do a package selection to customise the box is <prgn>tasksel</prgn>.
-The first Debian Integrated Solution Debian-Junior is mentioned in the
+The first Debian Pure Blend Debian Junior is mentioned in the
task selection list and thus it is clearly visible to the user who
installs Debian.
</p>
<p>
In bug <url id="http://bugs.debian.org/186085" name="#186085"> a
-request was filed to include Debian-Med in the same manner. The
+request was filed to include Debian Med in the same manner. The
problem with the <prgn>tasksel</prgn>-approach is that all included
packages should be on the first install CD. This would immediately
have the consequence that the first install CD would run out of space
-if all Debian Integrated Solutions would be included in the task
-selection list.
+if all Blends would be included in the task selection list.
</p>
<p>
-How to enhance visibility of Debian Integrated Solutions for the user
-who installs Debian from scratch?
+How to enhance visibility of Debian Pure Blends for the user who
+installs Debian from scratch?
<taglist>
<tag>Change <prgn>tasksel</prgn> policy.</tag>
<item>If the <em>packages must be on the first CD</em> feature of
- <prgn>tasksel</prgn> would be dropped all Debian Integrated
- Solutions could be listed under this topic in the task
- selection list.
+ <prgn>tasksel</prgn> would be dropped all Blends could be
+ listed under this topic in the task selection list.
</item>
- <tag>Debian Integrated Solutions information screen.</tag>
+ <tag>Debian Pure Blends information screen.</tag>
<item>Alternatively a new feature could be added to
<prgn>tasksel</prgn> or in addition to <prgn>tasksel</prgn>
in the installation procedure which presents a screen which
- gives some very short information about Debian Integrated
- Solutions (perhaps pointing to this document for further
- reference) and enables the user to select from a list of the
- available Debian Integrated Solutions.
+ gives some very short information about Debian Pure Blends
+ (perhaps pointing to this document for further reference) and
+ enables the user to select from a list of the available
+ Blends.
</item>
<tag>Provide separate install CDs</tag>
<item>By completely ignoring the installation of the official
- installation CD each Debian Integrated Solution can offer a
- separate installation CD. This will be done anyway for
- certain practical reasons (see for instance the Debian-Edu -
- SkoleLinux approach). But this is really no solution we
- could prefer because this does not work if the user wants to
- install more than one Debian Integrated Solution on one
- computer.
+ installation CD each Blend can offer a separate installation
+ CD. This will be done anyway for certain practical reasons
+ (see for instance the Debian Edu - SkoleLinux approach). But
+ this is really no solution we could prefer because this does
+ not work if the user wants to install more than one Blend on
+ one computer.
</item>
<tag>Change overall distribution philosophy of Debian.</tag>
<item>This way is concerned to some ideas from Debian developers
who took part in Open Source World Conference in Malaga and
- is explained in Detail in <ref
- id="new_ways_of_distribution">. This would save the problem
- of making Debian Integrated Solution visible to users in a
- completely different way because in this case Debian would be
- released as its various flavours of Debian Integrated
- Solutions.
+ is explained in Detail
+ in <ref id="new_ways_of_distribution">. This would save the
+ problem of making Debian Pure Blends visible to users in a
+ completely different way because in this case Debian would be
+ released as its various flavours of Blends.
</item>
</taglist>
</p>
@@ -136,122 +132,15 @@
invented to support them.
</p>
<sect1 id="webpages">
- <heading>Debian Integrated Solutions web pages</heading>
+ <heading>Debian Pure Blends web pages</heading>
<p>
-Most Debian Integrated Solutions maintain their own web space under
-<tt>http://www.debian.org/devel/DIS-name</tt> to provide general
+Some Blends maintain their own web space under
+<tt>http://www.debian.org/devel/BLEND-name</tt> to provide general
information which will be translated by the Debian web team. This is a
-good way to inform users about the progress of a project. A special
-way to announce what is done and what is planed is the list of yet
-packaged software and software which is intended to be included. To
-do this in a nice manner Tobias Toedter
-<email>t.toedter at gmx.net</email> defined a new tag for Debian Med
-in order to ease translation by making use of the
-<prgn>gettext</prgn> functionality. In the meantime, this new tag was
-extended to be useful for other Debian Integrated Solutions as well.
-</p>
-<p>
-As a result, a new <file>.pot</file> file was created, called
-<file>debian-cdd.pot</file>. Translators of the web pages should
-update their <file>.po</file> files and translate this new file into
-their language. For the translation teams who have already begun to
-translate the web pages of the Debian-Med Debian Integrated Solution,
-here is a short explanation of the newly introduced tag and its use.
-The tag is called <tt>project</tt>, and it takes a few attributes. The
-complete (empty) tag looks like this:
-
-<example>
-<project name=""
- url=""
- license=""
- deb=""
- anchorid="">
- Here goes the description of the project.
-</project>
-</example>
-
-The meaning of the attributes is as follows:
-
-<taglist>
- <tag>name</tag>
- <item>This is the name of the project which is yet packaged or
- should be packaged for the Debian Integrated Solution in
- question. In most cases, you won't have to translate this
- attribute.</item>
- <tag>url</tag>
- <item>This is the URL of the homepage of the project. You will
- almost never have to do any translational work here. At least
- I can't think of any.
- </item>
- <tag>license</tag>
- <item>The license under which the project is released. In most
- cases (e.g. GPL, BSD) you don't have to modify anything
- here. Some projects use a custom license or there's anything
- other which requires some more explanation in plain text. Of
- course, this plain text should be translated.
- </item>
- <tag>deb</tag>
- <item>This is the URL of a Debian package. If the project is
- available as an official Debian package (i.e. it is included
- in the Debian distribution or available in the contrib or
- non-free section) or if the project is being packaged by
- someone, but not stored on the Debian servers, this attribute
- is used. If there's no package available at all, this
- attribute is either left blank or omitted completely. There's
- no need to change this value in your translations.
- </item>
- <tag>anchorid</tag>
- <item>Every project gets an automatically created HTML anchor. This
- auto-anchor is created by using the project's name (Convert
- all ASCII characters into lowercase and replace any other
- character with the underscore. Silly example: "BioSig - For
- Everyone" -> "biosig___for_everyone"). If for some reason
- this is not wanted, the id and name of the anchor can be
- specified with this attribute. An example of the use of this
- attribute can be found in other.wml. The project's name is
- "HARP - HArmonisation for the secuRity of web technologies
- and aPplications", which is awfully long. The anchorid
- attribute in this case is set to "harp". Note that you should
- never have to change anything here, if it is already defined
- in the English page. If you have to translate the name of
- the project, the automatic creation of the anchorid will
- naturally give a different result then the English
- anchorid. In this case, please use this attribute to manually
- specify the anchor which should be used, according to the
- rules above: Convert all (ASCII) characters into lowercase,
- and replace any other character with an underscore. So in
- conclusion, you should always use the anchorid attribute if
- you've translated the name attribute.
- </item>
-</taglist>
-
-The interesting part of the <tt>project</tt>-tag is the body, between
-the opening and the closing tag. This is the description of the
-project, and this is the part where you're going to have to translate
-the text. The best way to learn the usage of this tag is to have a
-look at the Debian-Med examples.
-</p>
-<p>
-Moreover it might make sense to sort the list of projects according to
-the following keys:
-<taglist>
- <tag>available Debian package</tag>
- <item>Top most you should list all packages which are just inside
- Debian and thus (hopefully) included in the metapackage
- dependencies. This should be followed by the projects which
- has unofficial packages outside Debian. A last group should
- list all not yet packaged projects which are interesting for
- the Debian Integrated Solution. These groups are using a
- certain green-yellow-red color code.
- </item>
- <tag>alphabetically</tag>
- <item>Inside each of these three groups an alphabetical order is
- proposed to gain some consistency between all Debian
- Integrated Solutions.
- </item>
-</taglist>
-The users who are visiting the web pages will like this comfortable
-overview ...
+good way to inform users about the progress of a project. This page
+should link to the apropriate autogenerated pages as described
+in <ref id="web_if"> to make sure that the content of the page remains
+up to date at any time.
</p>
</sect1>
</sect>
@@ -281,35 +170,35 @@
<p>
Besides being able to perform package selection more efficiently by
being able to use a better categorisation, one of the first outcomes
-of Debian Package Tags for DISs is that every DIS could maintain its
-own set of tags organised under a "facet", providing categorisation
-data which could be used by its users and which automatically
-interrelates with the rest of the tags.
+of Debian Package Tags for Blends is that every Blend could maintain
+its own set of tags organised under a "facet", providing
+categorisation data which could be used by its users and which
+automatically interrelates with the rest of the tags.
</p>
<p>
-For example, Debian-Edu could look for "edu::administration" packages
+For example, Debian Edu could look for "edu::administration" packages
and then select "use::configuring". The "edu::administration"
-classification would be managed by the Debian-Edu people, while
+classification would be managed by the Debian Edu people, while
"use::configuring" would be managed by Debian. At the same time, non
-Debian-Edu users looking for "use::configuring" could have a look at
-what packages in that category are suggested by the Debian-Edu
+Debian Edu users looking for "use::configuring" could have a look at
+what packages in that category are suggested by the Debian Edu
community.
</p>
<p>
It is not excluded that this could evolve in being able to create a
-Debian Integrated Solution just by selecting all packages tagged by
-"edu::*" tags, plus dependencies; however, this option is still being
-investigated.
+Blend just by selecting all packages tagged by "edu::*" tags, plus
+dependencies; however, this option is still being investigated.
</p>
<p>
-Please write to the list <email>deb-usability-list at lists.alioth.debian.org</email>
-for more information about Debian Package Tags or if you want to get
+Please write to the
+list <email>deb-usability-list at lists.alioth.debian.org</email> for
+more information about Debian Package Tags or if you want to get
involved in Debian Package Tags development.
</p>
</sect>
<sect id="EnhancingTechnology">
- <heading>Enhancing basic technologies regarding Debian Integrated Solutions</heading>
+ <heading>Enhancing basic technologies regarding Debian Pure Blends</heading>
<p>
In section <ref id="future_handling"> several issues where raised how
@@ -341,19 +230,19 @@
<p>
If there is some agreement to use <prgn>cfengine</prgn> scripts to
change configuration - either according to <prgn>debconf</prgn>
-questions or even to adapt local configuration for Debian Integrated
-Solution use in general - a common location for this kind of stuff
-should be found. Because these scripts are not configuration itself
-but substantial part of a metapackage the suggestion would be to
-store this stuff under
+questions or even to adapt local configuration for Debian Pure Blend
+use in general - a common location for this kind of stuff should be
+found. Because these scripts are not configuration itself but
+substantial part of a metapackage the suggestion would be to store
+this stuff under
<example>
- /usr/share/dis/#DIS#/#METAPACKAGE#/cf.#SOMETHING#
+ /usr/share/blends/#BLEND#/#METAPACKAGE#/cf.#SOMETHING#
</example>
</p>
<p>
There was another suggestion at the Valencia workshop: Make use of
<prgn>ucf</prgn> for the purpose mentioned above. This is a topic
-for discussion. At least currently Debian-Edu seems to have good
+for discussion. At least currently Debian Edu seems to have good
experiences with <prgn>cfengine</prgn> but perhaps it is worth comparing
both.
</p>
@@ -365,7 +254,7 @@
</sect>
<sect id="liveCD">
- <heading>Building Live CDs of each Debian Integrated Solution</heading>
+ <heading>Building Live CDs of each Debian Pure Blend</heading>
<p>
The first step to convince a user to switch to Debian is to show him
@@ -382,9 +271,10 @@
thus people started to adopt it for there special needs. In fact
there exist so many Debian based Live CDs that it makes hardly sense
to list them all here. The main problem is that most of them
-containing special applications and thus are interesting in the DIS
+containing special applications and thus are interesting in the Blends
scope are out of date because they way the usually were builded was a
-pain. One exception is perhaps <url id="http://dirk.eddelbuettel.com/quantian.html"
+pain. One exception is
+perhaps <url id="http://dirk.eddelbuettel.com/quantian.html"
name="Quantian"> which is quite regularly updated and is intended for
scientists.
</p>
@@ -392,10 +282,10 @@
The good news is that the problem of orphaned or outdated Live CDs can
easily solved by debian-live and the <package>live-helper</package>.
This package turns all work to get an up to date ISO image for a Live
-CD into calling a single script. For the DIS tools this would simply
-mean that the tasks files have to be turned into a live-helper input
-file and the basic work is done. This will be done in a future
-dis-dev version.
+CD into calling a single script. For the Blends tools this would
+simply mean that the tasks files have to be turned into a live-helper
+input file and the basic work is done. This will be done in a future
+<package>blends-dev</package> version.
</p>
</sect>
@@ -421,22 +311,22 @@
process which propagates packages to <tt>testing</tt> and releasing a
complete <tt>stable</tt> distribution also remains untouched. The new
thing is that the package pool could be enhanced to store more package
-versions which belong to certain subsets alias Debian Integrated
-Solutions which all have a set of <tt>tested inside the
-subset</tt> distribution which leads to a <tt>stable</tt> subset
-release. The following graph might clarify this:
+versions which belong to certain subsets alias Debian Pure Blends
+which all have a set of <tt>tested inside the subset</tt> distribution
+which leads to a <tt>stable</tt> subset release. The following graph
+might clarify this:
<example>
-DD -> unstable --> testing --> stable
+DD -> unstable --> testing --> stable
|
- +---> DIS_A testing --> stable DIS_A
+ +---> BLEND_A testing --> stable BLEND_A
|
- +---> DIS_B testing --> stable DIS_B
+ +---> BLEND_B testing --> stable BLEND_B
|
+---> ...
</example>
-where <tt>DIS_A</tt> / <tt>DIS_B</tt> might be something like
+where <tt>BLEND_A</tt> / <tt>BLEND_B</tt> might be something like
<tt>debian-edu</tt> / <tt>debian-med</tt>. To implement this
sub-setting the following things are needed:
<taglist>
@@ -447,15 +337,15 @@
<email>madkiss at debian.org</email> announced exactly this as
"nearly implemented for testing purpose" which should solve
the problem of outdated software for desktop users as a goal
- of the <tt>debian-desktop</tt> project.
+ of the <tt>debian-desktop</tt> project. Unfortunately this
+ goal was not realised finally.
</item>
<tag>Reasonable subsets</tag>
<item>Once the promotion tools are able to work with sub-setting,
reasonable subsets have to be defined and maintained. A
- decision has to be made (if this will be implemented at all)
- whether this sub-setting should be done according to the
- Debian Integrated Solution layout or if there are better ways
- to find subsets.
+ decision has to be made (if this will be implemented at all)
+ whether this sub-setting should be done according to the
+ Blend layout or if there are better ways to find subsets.
</item>
<tag>BTS support</tag>
<item>The Bug Tracking System has to deal with different package
@@ -464,24 +354,24 @@
</item>
<tag>Security</tag>
<item>As a consequence of having more than only a single
- <tt>stable</tt> each DIS-team has to form a security team to
- care for those package versions that are not identically with
- the "old" <tt>stable</tt>.
+ <tt>stable</tt> each Blend team has to form a security team
+ to care for those package versions that are not identically
+ with the "old" <tt>stable</tt>.
</item>
</taglist>
</p>
<p>
A not so drastically change would be to find a <em>common</em> set of
-packages which are interesting for all Debian Integrated Solutions
-which will obtained from the "releasable set" of testing (i.e. no
+packages which are interesting for all Debian Pure Blends which will
+obtained from the "releasable set" of testing (i.e. no
RC-bugs). This would make the structure above a little bit more flat:
<example>
DD -> unstable --> testing --> releasable --> stable
|
- +---> stable DIS_A
+ +---> stable BLEND_A
|
- +---> stable DIS_B
+ +---> stable BLEND_B
|
+---> ...
</example>
@@ -496,34 +386,33 @@
v
DD -> unstable --> testing --> stable
|
- +---> stable DIS_A
+ +---> stable BLEND_A
|
- +---> stable DIS_B
+ +---> stable BLEND_B
|
+---> ...
</example>
The rationale behind these testing backports is that sometimes a
-Debian Integrated Solution is able to reduce the set of releasable
-architectures. Thus some essential packages could be moved much
-faster to testing and these might be "backported" to testing for this
-special Debian Integrated Solution. For instance this might make
-sense for Debian-Edu where usually i386 architecture is used.
+Debian Pure Blend is able to reduce the set of releasable
+architectures. Thus some essential packages could be moved much
+faster to testing and these might be "backported" to testing
+for this special Blend. For instance this might make sense for Debian
+Edu where usually neither mainframes nor embedded devices are used.
</p>
<p>
All these different suggestions would lead to a modification of the
package pool scripts which could end up in a new way to distribute
-Debian. This might result from the fact that some Debian Integrated
-Solutions need a defined release cycle. For instance the
-education related distributions might trigger their release by the
-start-end-cycle of the school year. Another reason to change the
-package pool system is the fact that some interested groups, who
-provide special service for a certain Debian Integrated Solution,
-would take over support only for the subset of packages which is
-included in the metapackage dependencies or suggestions but they
-refuse to provide full support for the whole range of Debian
-packages. This would lead to a new layout of the file structures of
-the Debian mirrors:
+Debian. This might result from the fact that some Debian Pure Blends
+need a defined release cycle. For instance the education related
+distributions might trigger their release by the start-end-cycle of
+the school year. Another reason to change the package pool system is
+the fact that some interested groups, who provide special service for
+a certain Blend, would take over support only for the subset of
+packages which is included in the metapackage dependencies or
+suggestions but they refuse to provide full support for the whole
+range of Debian packages. This would lead to a new layout of the file
+structures of the Debian mirrors:
<example>
debian/dists/stable/binary-i386
@@ -531,38 +420,36 @@
/binary-...
/testing/...
/unstable/...
- debian-DIS_A/dists/stable/binary-[supported_architecture1]
- /binary-[supported_architecture2]
+ debian-BLEND_A/dists/stable/binary-[supported_architecture1]
+ /binary-[supported_architecture2]
/...
- /testing/...
- debian-DIS_B/dists/testing/...
- /stable/...
+ /testing/...
+ debian-BLEND_B/dists/testing/...
+ /stable/...
...
pool/main
/contrib
/non-free
</example>
To avoid flooding the archive with unnecessarily many versions of
-packages for each single Debian Integrated Solution a common base of
-all these Debian Integrated Solutions has to be defined. Here some
-LSB conformance statement comes into mind: The base system of all
-currently released (stable) Debian Integrated Solutions is compliant
-to LSB version x.y.
+packages for each single Debian Pure Blend a common base of all these
+Blends has to be defined. Here some LSB conformance statement comes
+into mind: The base system of all currently released (stable) Debian
+Pure Blends is compliant to LSB version x.y.
</p>
<p>
Regarding to security issues there are two ways: Either one Debian
-Integrated Solution goes with the current stable Debian and thus the
+Pure Blend goes with the current stable Debian and thus the
<file>Packages.gz</file> is just pointing to the very same versions
which are also in debian/stable. Then no extra effort regarding to
security issues is need. But if there would be a special support team
which takes over maintenance and security service for the packages in
-one certain Debian Integrated Solution they should be made reliable
-for this certain subset.
+a certain Blend they should be made reliable for this certain subset.
</p>
<p>
-This reduced subset of Debian packages of a Debian Integrated Solution
-would also make it easier to provide special install CDs at is it
-currently done by Debian Edu.
+This reduced subset of Debian packages of a Debian Pure Blend would
+also make it easier to provide special install CDs at is it currently
+done by Debian Edu.
</p>
</sect>
</chapt>
@@ -578,7 +465,7 @@
sgml-always-quote-attributes:t
sgml-indent-step:2
sgml-indent-data:t
-sgml-parent-document:("../debian-dis.en.sgml" "book" "chapt")
+sgml-parent-document:("../debian-blends.en.sgml" "book" "chapt")
sgml-exposed-tags:nil
sgml-local-catalogs:nil
sgml-local-ecat-files:nil
Modified: blends/trunk/blends/doc/en/A_devel.sgml
==============================================================================
--- blends/trunk/blends/doc/en/A_devel.sgml (original)
+++ blends/trunk/blends/doc/en/A_devel.sgml Sun Nov 9 08:22:05 2008
@@ -1,53 +1,53 @@
<appendix id="DevelDescription">
<heading>Description of development tools</heading>
- <sect id="dis-dev">
- <heading>Package <package>dis-dev</package></heading>
+ <sect id="blends-dev">
+ <heading>Package <package>blends-dev</package></heading>
<p>
If metapackages are builded using the tools inside the
-<package>dis-dev</package> package it can be ensured that the
+<package>blends-dev</package> package it can be ensured that the
resulting metapackages will work nicely with the same version of
-<package>dis-common</package> package. The goal is to keep necessary
-changes for the source of the metapackages of a Custom Debian
-Distribution as low as possible when the version of the
-<package>dis</package> source package changes. Thus it is
+<package>blends-common</package> package. The goal is to keep
+necessary changes for the source of the metapackages of a Debian Pure
+Blend as low as possible when the version of the
+<package>blends</package> source package changes. Thus it is
strongly recommended to use the tools described below.
</p>
<p>
-The usage of the tools in the <package>dis-dev</package> package might
+The usage of the tools in the <package>blends-dev</package> package might
introduce a versioned dependency in the
-<package><var><dis></var>-common</package> package from which
-all other metapackages of the <var>DIS</var> in question will
-depend. This <package><var><dis></var>-common</package> package
-instantiates the <var>DIS</var> in the common registry for all DISs in
-<file>/etc/dis</file>.
+<package><var><blend></var>-config</package> package from which
+all other metapackages of the <var>Blend</var> in question will
+depend. This <package><var><blend></var>-config</package> package
+instantiates the <var>Blend</var> in the common registry for all Blends in
+<file>/etc/blends</file>.
</p>
<p>
The best idea to use the tools provided by the
-<package>dis-dev</package> is to put a <file>Makefile</file> into the
+<package>blends-dev</package> is to put a <file>Makefile</file> into the
build directory containig one single line
<example>
- include /usr/share/dis-dev/Makefile
+ include /usr/share/blends-dev/Makefile
</example>
-(see <file>/usr/share/doc/dis-dev/examples/Makefile</file>). Using
+(see <file>/usr/share/doc/blends-dev/examples/Makefile</file>). Using
this <file>Makefile</file> all tools that were contained in
-<package>dis-dev</package> package versions before 0.4. These tools
-are moved to <file>/usr/share/dis-dev/</file> because there is no need
+<package>blends-dev</package> package versions before 0.4. These tools
+are moved to <file>/usr/share/blends-dev/</file> because there is no need
to call them directly. Here is a list of the <file>make</file> targets.
</p>
-<sect1 id="dis-tasks.desc">
- <heading>DIS<tt>-tasks.desk</tt></heading>
+<sect1 id="blends-tasks.desc">
+ <heading>Blend<tt>-tasks.desk</tt></heading>
<p>
This target is the description file that is used in
<prgn>tasksel</prgn> to enable selecting the tasks belonging to the
-DIS. The file will be moved to the
-<var>dis</var><package>-tasks</package>. All information is obtained
+Blend. The file will be moved to the
+<var>blend</var><package>-tasks</package>. All information is obtained
from the single task files in the <file>tasks</file> directory of the
-DIS source.
+Blend source.
</p>
</sect1>
@@ -55,14 +55,14 @@
<heading><tt>debian/control</tt></heading>
<p>
-The <file>debian/control</file> file of a DIS metapackage source
+The <file>debian/control</file> file of a Blend metapackage source
archive is auto generated out of dependencies that are specified in so
called <file>tasks</file> files. The rationale behind this is to
enhance flexibility about changes inside the Debian package pool where
new packages might appear and others might be renamed.
-The <file>tasks</file> just define which dependencies the DIS
+The <file>tasks</file> just define which dependencies the Blend
maintainer group wants to be fulfilled and the
-script <prgn>dis-gen-control</prgn> verifies whether these
+script <prgn>blend-gen-control</prgn> verifies whether these
dependencies exist in the specified package pool and create
the <file>debian/control</file> file according to the available
packages. This does not only work for the Debian package pool
@@ -118,19 +118,19 @@
of the metapackage. Packages that are specified with
"Suggests" will not be taken over to
the <prgn>tasksel</prgn> control file
- (DIS<file>-tasks.desk</file>,
- see <ref id="dis-tasks.desc">) but only to the list of
+ (Blend<file>-tasks.desk</file>,
+ see <ref id="blends-tasks.desc">) but only to the list of
suggested packages of the according metapackage.
</item>
<tag>Ignore</tag>
<item>The "Ignore" key can be used as kind of "Soft-Suggests"
- to put a package on the radar of the DIS. Packages that
+ to put a package on the radar of the Blend. Packages that
are tagged with Ignore will not be taken over into the
list of dependencies inside
the <file>debian/control</file> file of the resulting
- metapackage neither to the DIS<file>-tasks.desk</file>
+ metapackage neither to the Blend<file>-tasks.desk</file>
control file for <prgn>tasksel</prgn> but will be taken
- over onto the installation medium of a DIS in case there
+ over onto the installation medium of a Blend in case there
is some space left. This key becomes especially
important for specifying not yet packaged software that
might be packaged in the future (prospective packages).
@@ -142,63 +142,28 @@
be listed in the the <file>debian/control</file> file as
"Recommends" or "Suggests" but, should not go to a
installation medium (CD, DVD, etc.) that might be
- produced by the DIS. A reason to avoid a package might
+ produced by the Blend. A reason to avoid a package might
be that it belongs to the non-free section.
</item>
</taglist>
</p>
</sect1>
-<sect1 id="dis-clean-helper">
- <heading><!-- document type does not allow element "MANREF" here--><tt>dis-clean-helper(1)</tt></heading>
-
-<p>
-<taglist>
- <tag>NAME</tag>
- <item>
- <prgn>dis-clean-helper</prgn> - cleans up debian directory in a
- metapackage building tree
- </item>
- <tag>SYNOPSIS</tag>
- <item>
- <prgn>dis-clean-helper</prgn>
- </item>
- <tag>DESCRIPTION</tag>
- <item>
- <p>
- This script can be used in <file>debian/rules</file> file to
- revert the changes which were done by <manref
- name="dis-install-helper" section="1"> to get a clean packaging
- tree. Using this helper ensures that the
- <file>debian/rules</file> file does not needed to be changed if
- there are changes in the <package>dis-dev</package> package.
- </p>
- </item>
- <tag>EXAMPLES</tag>
- <item>For the usage of this tool just have a look at the
- <package>debian-med</package> source package.
- </item>
- <tag>AUTHOR</tag>
- <item>Andreas Tille <email>tille at debian.org</email>.</item>
- </taglist>
-</p>
-</sect1>
-
<sect1>
- <heading>Apt <file>sources.list</file> files in <file>/etc/dis/</file></heading>
+ <heading>Apt <file>sources.list</file> files in <file>/etc/blends/</file></heading>
<p>
-These files are used by <manref name="dis-gen-control" section="1"> to
+These files are used by <manref name="blend-gen-control" section="1"> to
build valid <file>debian/control</file> files that contain only
available packages in their dependencies. This enables building meta
packages for <tt>stable</tt>, <tt>testing</tt>, <tt>unstable</tt> or
even a completely different distribution that has valid
<file>sources.list</file> entries. The file
-<file>/etc/dis/control.list</file> is used as default for <manref
-name="dis-gen-control" section="1"> and usually is a symbolic link
+<file>/etc/blends/control.list</file> is used as default for <manref
+name="blend-gen-control" section="1"> and usually is a symbolic link
(see <manref name="ln" section="1">) to
<file>sources.list.</file><var>distribution</var>. It might be
changed using the <tt>-s </tt><var>dist</var> option of <manref
-name="dis-gen-control" section="1">.
+name="blend-gen-control" section="1">.
</p>
<p>
<strong>TODO:</strong> <em>Either parse the available
@@ -208,56 +173,56 @@
</sect1>
<sect1>
- <heading>Templates in <file>/usr/share/dis/templates</file></heading>
+ <heading>Templates in <file>/usr/share/blends/templates</file></heading>
<p>
-The directory <file>/usr/share/dis/templates</file> contains templates
-that can be used to build a <var><dis></var><package>-common</package>,
+The directory <file>/usr/share/blends/templates</file> contains templates
+that can be used to build a <var><blend></var><package>-config</package>,
which uses the tools that are contained in the
-<package>dis-common</package> package, and are useful to manage
-<var><dis></var> user groups (see <ref id="userroles">).
+<package>blends-common</package> package, and are useful to manage
+<var><blend></var> user groups (see <ref id="userroles">).
</p>
</sect1>
</sect>
-<sect id="dis-common">
- <heading>Package <package>dis-common</package></heading>
+<sect id="blends-common">
+ <heading>Package <package>blends-common</package></heading>
<p>
-This package creates a common registry for all DISs in
-<file>/etc/dis</file>. Each DIS should put the files that are used
-into a subdirectory named like the DIS of <file>/etc/dis</file>. The
-<package>dis-common</package> package installs a common configuration
-file <file>/etc/dis/dis.conf</file>, which can be used to influence the
+This package creates a common registry for all Blends in
+<file>/etc/blends</file>. Each Blend should put the files that are used
+into a subdirectory named like the Blend of <file>/etc/blends</file>. The
+<package>blends-common</package> package installs a common configuration
+file <file>/etc/blends/blends.conf</file>, which can be used to influence the
behaviour of the tools described below.
</p>
<sect1>
- <heading><!-- document type does not allow element "MANREF" here--><tt>dis-role(8)</tt></heading>
+ <heading><!-- document type does not allow element "MANREF" here--><tt>blend-role(8)</tt></heading>
<p>
<taglist>
<tag>NAME</tag>
<item>
- <prgn>dis-role</prgn> - add/remove roles in registered Debian Integrated Solution
+ <prgn>blend-role</prgn> - add/remove roles in registered Debian Pure Blend
</item>
<tag>SYNOPSIS</tag>
<item>
- <prgn>dis-role</prgn> <var>add|del</var> <var>DIS</var> [<var>Role</var>]
+ <prgn>blend-role</prgn> <var>add|del</var> <var>Blend</var> [<var>Role</var>]
</item>
<tag>DESCRIPTION</tag>
<item>Add/remove (register/unregister) <var>Role</var> for the
- specified <var>DIS</var>. If <var>Role</var> is not specified, it's
- assumed to be named like <var>DIS</var>.
+ specified <var>Blend</var>. If <var>Role</var> is not specified, it's
+ assumed to be named like <var>Blend</var>.
</item>
<tag>OPTIONS</tag>
<item>
<taglist>
- <tag><var>DIS</var></tag>
- <item>A registered custom distribution in /etc/dis, for example
- one of <tt>med</tt>, <tt>junior</tt>, <tt>desktop</tt>,
- <tt>edu</tt> or <tt>demudi</tt>
+ <tag><var>Blend</var></tag>
+ <item>A registered Blend in /etc/blends, for example
+ one of <tt>med</tt>, <tt>junior</tt>,
+ <tt>edu</tt> or <tt>science</tt>
</item>
</taglist>
</item>
@@ -268,24 +233,24 @@
</p>
</sect1>
-<sect1 id="dis-update-menus">
+<sect1 id="blend-update-menus">
<heading><!-- document type does not allow element "MANREF"
- here--><tt>dis-update-menus(8)</tt></heading>
+ here--><tt>blend-update-menus(8)</tt></heading>
<p>
<taglist>
<tag>NAME</tag>
<item>
- <prgn>dis-update-menus</prgn> - add menu of metapackage to all Debian Integrated Solution users
+ <prgn>blend-update-menus</prgn> - add menu of metapackage to all Blend users
</item>
<tag>SYNOPSIS</tag>
<item>
- <prgn>dis-update-menus</prgn> [<var>--dis DIS</var> | <var>--user
+ <prgn>blend-update-menus</prgn> [<var>--blend Blend</var> | <var>--user
user</var>]
</item>
<tag>DESCRIPTION</tag>
<item>
<p>
- dis-update-menus behaves differently depending on who run the
+ blend-update-menus behaves differently depending on who run the
command:
</p>
@@ -295,18 +260,18 @@
</p>
<p>
- If it is called by root, it adds and keeps updated user's menu entries
- (see menu package for users' menus) for all users who belong to the
- group of the specified Debian Integrated Solution, or only for a
- specified user, depending on which parameter is passed to the script.
+ If it is called by root, it adds and keeps updated user's menu
+ entries (see menu package for users' menus) for all users who
+ belong to the group of the specified Blend, or only for a specified
+ user, depending on which parameter is passed to the script.
</p>
</item>
<tag>OPTIONS</tag>
<item>
<taglist>
- <tag><var>DIS</var></tag>
- <item>one of the installed DISs, listed in /etc/dis/, for example
+ <tag><var>Blend</var></tag>
+ <item>one of the installed Blends, listed in /etc/blends/, for example
(if installed: <tt>med</tt>, <tt>junior</tt>, <tt>desktop</tt>,
<tt>edu</tt> or <tt>demudi</tt>
</item>
@@ -322,38 +287,38 @@
</sect1>
<sect1>
- <heading><!-- document type does not allow element "MANREF" here--><tt>dis-user(8)</tt></heading>
+ <heading><!-- document type does not allow element "MANREF" here--><tt>blend-user(8)</tt></heading>
<p>
<taglist>
<tag>NAME</tag>
<item>
- <prgn>dis-user</prgn> - add/remove user to Role of a registered Debian Integrated Solution
+ <prgn>blend-user</prgn> - add/remove user to Role of a registered Blend
</item>
<tag>SYNOPSIS</tag>
<item>
- <prgn>dis-user</prgn> <var>add|del</var> <var>DIS</var> <var>user</var> [<var>Role</var>]
+ <prgn>blend-user</prgn> <var>add|del</var> <var>Blend</var> <var>user</var> [<var>Role</var>]
</item>
<tag>DESCRIPTION</tag>
- <item>Add/remove user to a <var>Role</var> of the specified <var>DIS</var>.
+ <item>Add/remove user to a <var>Role</var> of the specified <var>Blend</var>.
If <var>Role</var> is not specified, it's assumed to be named like
- <var>DIS</var>
+ <var>Blend</var>
</item>
<tag>OPTIONS</tag>
<item>
<taglist>
- <tag><var>DIS</var></tag>
- <item>A registered custom distribution in /etc/dis, for example
- one of <tt>med</tt>, <tt>junior</tt>, <tt>desktop</tt>,
- <tt>edu</tt> or <tt>demudi</tt>
+ <tag><var>Blend</var></tag>
+ <item>A registered Blend in /etc/blends, for example
+ one of <tt>med</tt>, <tt>junior</tt>,
+ <tt>edu</tt> or <tt>science</tt>.
</item>
<tag><var>user</var></tag>
<item>user to add</item>
<tag><var>Role</var></tag>
- <item>the role in the <var>DIS</var> that <var>user</var> will
+ <item>the role in the <var>Blend</var> that <var>user</var> will
assume</item>
</taglist>
</item>
@@ -365,21 +330,21 @@
</sect1>
<sect1>
- <heading><tt>dis.conf(5)</tt></heading>
+ <heading><tt>blends.conf(5)</tt></heading>
<p>
<taglist>
<tag>NAME</tag>
<item>
- <file>dis.conf</file> - configuration for Debian Integrated Solution registry
+ <file>blends.conf</file> - configuration for Debian Pure Blends registry
</item>
<tag>DESCRIPTION</tag>
- <item>This file is sourced from shell scripts inside the Custom
- Debian Distribution package <package>dis-common</package> and
- thus it has to follow shell syntax. The variables that are set
- inside this configuration file can be overriden by special DIS
- configration files
- <file>/etc/dis/<var><>dis></var>/<var><>dis></var>.conf</file>
- for each single DIS.
+ <item>This file is sourced from shell scripts inside the Debian
+ Pure Blends package <package>blends-common</package> and thus
+ it has to follow shell syntax. The variables that are set
+ inside this configuration file can be overriden by special
+ Blend configration files
+ <file>/etc/blends/<var><>Blend></var>/<var><>Blend></var>.conf</file>
+ for each single Blend.
<tag>SYNTAX</tag>
<item>The following variables can be set:
<taglist>
@@ -394,9 +359,8 @@
packages can be created automatically at install time of
the package if the postinst script of the package allows
this. It is suggested to use this option in the specific
- configuration files of a special Custom Debian
- Distribution that override the settings of the general
- configuration file.
+ configuration files of a special Debian Pure Blend that
+ override the settings of the general configuration file.
</item>
<tag><tt>SHAREDIR</tt></tag>
<item>Set the base directory for the user role management
@@ -416,8 +380,8 @@
</item>
<tag>SEE ALSO</tag>
<item>
- <file>dis-role (8)</file>, <file>dis-update-menus (8)</file>,
- <file>dis-user (8)</file>
+ <file>blend-role (8)</file>, <file>blend-update-menus (8)</file>,
+ <file>blend-user (8)</file>
</item>
<tag>AUTHOR</tag>
<item>Andreas Tille <email>tille at debian.org</email>,
@@ -433,20 +397,20 @@
<heading>Working with <file>svn</file></heading>
<p>
Sometimes it might be interesting for developers to check out the
- latest code of the DIS tools or a special DIS code for the meta
+ latest code of the Blend tools or a special Blend code for the meta
packages. In <ref id="communication"> the directory layout of the
<file>svn</file>-directory was described. How to derive the
Debian packages from this layout?
<taglist>
<tag>Checkout</tag>
<item>
- For the DIS tools
+ For the Blend tools
<example>
- svn checkout svn+ssh://<var>username</var>@svn.debian.org/svn/cdd/cdd/trunk/dis dis
+ svn checkout svn+ssh://<var>username</var>@svn.debian.org/svn/cdd/blends/trunk/blends blends
</example>
- or for the Debian Integrated Solution <var>dis-name</var>
+ or for the Debian Pure Blend <var>BLEND-name</var>
<example>
- svn checkout svn+ssh://<var>username</var>@svn.debian.org/svn/cdd/projects/<var>dis-name</var>/trunk
+ svn checkout svn+ssh://<var>username</var>@svn.debian.org/svn/cdd/projects/<var>BLEND-name</var>/trunk
</example>
</item>
<tag>Build source package</tag>
@@ -460,7 +424,7 @@
file <file>Makefile</file> in your package source directory containing
<example>
#!/usr/bin/make -f
- include /usr/share/dis-dev/Makefile
+ include /usr/share/blends-dev/Makefile
</example>
Which enables you to simply say
<example>
@@ -493,7 +457,7 @@
sgml-always-quote-attributes:t
sgml-indent-step:2
sgml-indent-data:t
-sgml-parent-document:("../debian-dis.en.sgml" "book" "chapt")
+sgml-parent-document:("../debian-blends.en.sgml" "book" "chapt")
sgml-exposed-tags:nil
sgml-local-catalogs:nil
sgml-local-ecat-files:nil
Modified: blends/trunk/blends/doc/en/B_quickintro.sgml
==============================================================================
--- blends/trunk/blends/doc/en/B_quickintro.sgml (original)
+++ blends/trunk/blends/doc/en/B_quickintro.sgml Sun Nov 9 08:22:05 2008
@@ -21,13 +21,13 @@
<p>
This howto describes the building of metapackages by using the
-<package>dis-dev</package> package. It is perfectly possible to build
-a metapackage as any other normal Debian package but this HOWTO
+<package>blends-dev</package> package. It is perfectly possible to
+build a metapackage as any other normal Debian package but this HOWTO
has the only purpose to describe the profit you might gain by using
these tools.
<example>
-~> cp -a /usr/share/doc/dis-dev/examples/tasks .
+~> cp -a /usr/share/doc/blends-dev/examples/tasks .
~> cat tasks/README
~> edit tasks/task1
Description: <var>short description
@@ -38,7 +38,7 @@
For each metapackage this skeleton of a <file>debian/control</file>
entry is needed. All necessary information is available in the
-directory <file>/usr/share/doc/dis-dev/examples/tasks</file>.
+directory <file>/usr/share/doc/blends-dev/examples/tasks</file>.
</p>
</sect>
@@ -48,28 +48,28 @@
<p>
To build any Debian package you always need a directory named
<file>debian</file>, which contains a certain set of files. The
-package <package>dis-dev</package> provides a complete set of example
+package <package>blends-dev</package> provides a complete set of example
files that only have to be copied and after editing some place
holders are ready to use.
<example>
-~> cp -a /usr/share/doc/dis-dev/examples/debian .
+~> cp -a /usr/share/doc/blends-dev/examples/debian .
~> cat debian/README
~> edit debian/control.stub
</example>
Now the variables in the file <file>control.stub</file> change the
-variables named <var>_DIS_</var>, <var>_MAINTAINER_</var> etc. to
-match the names of the Debian Integrated Solution to be built. Please
-note that the file <file>debian/control</file> is and has to be a
-symbolic link to <file>control.stub</file> to let the
-<package>dis-dev</package> tools work.
+variables named <var>_BLEND_</var>, <var>_MAINTAINER_</var> etc. to
+match the names of the Debian Pure Blend to be built. Please note
+that the file <file>debian/control</file> is and has to be a symbolic
+link to <file>control.stub</file> to let the
+<package>blends-dev</package> tools work.
<example>
~> edit debian/rules
</example>
-Also in the <file>debian/rules</file> the name of the Custom Debian
-Distribution has to be inserted where the template contains
-<var>_DIS_</var>. Depending from the way the
+Also in the <file>debian/rules</file> the name of the Blend has to be
+inserted where the template contains
+<var>_BLEND_</var>. Depending from the way the
<file>sources.list</file> should be scanned the options for the
<prgn>gen-control</prgn> call can be adjusted.
</p>
@@ -82,7 +82,7 @@
<file>Makefile</file> containing
<example>
#!/usr/bin/make -f
-include /usr/share/dis-dev/Makefile
+include /usr/share/blends-dev/Makefile
</example>
which enables you to simply use
<example>
@@ -100,7 +100,7 @@
That's all for the very simple case when the metapackages should not
contain user menus. Even if user menus are suggested they are not
necessary. The following paragraphs describe how to use the
-<package>dis-dev</package> tools to support these menus.
+<package>blends-dev</package> tools to support these menus.
</p>
</sect>
@@ -112,22 +112,22 @@
The creation of a common package is optional, but suggested, because it
adds some special features like menus, user groups, and probably more
in the future. It is automatically built by
-<file>dis-install-helper</file>, which is called in
+<file>blend-install-helper</file>, which is called in
<file>debian/rules</file>, if the <file>common</file> directory exists.
The easiest way to create this is as follows:
<example>
-~> cp -a /usr/share/doc/dis-dev/examples/common .
+~> cp -a /usr/share/doc/blends-dev/examples/common .
~> cat common/README
~> edit common/conf common/control common/common.1
</example>
-The variables (<var>_DIS_</var>) in these three files have to be
-adjusted to the name of the Debian Integrated Solution in question.
-This <file><var>dis</var>-common</file> cares for the initialisation
+The variables (<var>_BLEND_</var>) in these three files have to be
+adjusted to the name of the Debian Pure Blend in question.
+This <file><var>blend</var>-config</file> cares for the initialisation
of the role based menu system and might contain adjustments of the
-general configuration inside the <package>dis-common</package>.
+general configuration inside the <package>blends-common</package>.
</p>
<p>
-If the metapackage <package><var>dis</var>-common</package> will be
+If the metapackage <package><var>blend</var>-config</package> will be
created according to these rules all other metapackages will depend
automatically from this common package. For the friends of
<prgn>auto-apt</prgn>, a helper
@@ -144,10 +144,10 @@
<p>
As explained in <ref id="menu_tools"> the metapackages can contain
user menus. This optional feature can be implemented easily by using
-the template from the <package>dis-dev</package> in the following way:
+the template from the <package>blends-dev</package> in the following way:
<example>
-~> cp -a /usr/share/doc/dis-dev/examples/menu .
+~> cp -a /usr/share/doc/blends-dev/examples/menu .
~> cat menu/README
~> edit menu/task1
<var>Edit the example to legal menu entries of the
@@ -162,12 +162,12 @@
The only thing that has to be changed in these menu entries is the
<tt>package</tt> field, which has to be changed from
<package><dependent package></package> to
-<package><var>dis</var>-<var>task</var></package>. All other entries
+<package><var>blend</var>-<var>task</var></package>. All other entries
might remain unchanged. This is a good point to check whether the
menu entries of the packages you depend from are formated nicely and
print the necessary information (for instance make use of "hints").
Here the metapackage maintainer has a good chance for quality
-assurance work, which is also part of the Debian Integrated Solutions
+assurance work, which is also part of the Debian Pure Blends
issue.
</p>
<p>
@@ -176,7 +176,7 @@
script of the metapackage because it is granted that the needed menu
files are installed on the system, which is not really necessary on
the metapackage build machine. This might be implemented in later
-versions of <package>dis-dev</package>. Currently the policy is that
+versions of <package>blends-dev</package>. Currently the policy is that
we like to have a little bit of control about the menu entries for the
quality assurance issue mentioned above. Last, but not least, there are
packages that do not provide a menu entry. If this is the case
@@ -200,7 +200,7 @@
the following templates:
<example>
-~> cp -a /usr/share/doc/dis-dev/examples/docs .
+~> cp -a /usr/share/doc/blends-dev/examples/docs .
~> cat docs/README
~> edit docs/task1/dep1
<var>Provide information about a package <dep1> that is
@@ -229,7 +229,7 @@
sgml-always-quote-attributes:t
sgml-indent-step:2
sgml-indent-data:t
-sgml-parent-document:("../debian-dis.en.sgml" "book" "chapt")
+sgml-parent-document:("../debian-blends.en.sgml" "book" "chapt")
sgml-exposed-tags:nil
sgml-local-catalogs:nil
sgml-local-ecat-files:nil
Modified: blends/trunk/blends/doc/en/C_bts.sgml
==============================================================================
--- blends/trunk/blends/doc/en/C_bts.sgml (original)
+++ blends/trunk/blends/doc/en/C_bts.sgml Sun Nov 9 08:22:05 2008
@@ -6,10 +6,10 @@
<p>
A very frequently asked question in mailing list is, whether
-<prgn>program_xy</prgn> can be integrated into a Custom Debian
-Distribution. As long as there is an official package of this program
-it is an easy task. But mostly users ask for software which is not yet
-integrated into Debian.
+<prgn>program_xy</prgn> can be integrated into a Debian Pure Blend.
+As long as there is an official package of this program it is an easy
+task. But mostly users ask for software which is not yet integrated
+into Debian.
</p>
<p>
There is a <url id="http://www.debian.org/devel/wnpp/#l1"
@@ -19,9 +19,9 @@
</p>
<p>
If you use wnpp sanely you can even tag this bug for the intended
-purpose to include it in a certain Debian Integrated Solution. This
-was described in <url
-id="http://lists.debian.org/debian-devel-announce/2005/09/msg00002.html"
+purpose to include it in a certain Debian Pure Blend. This was
+described
+in <url id="http://lists.debian.org/debian-devel-announce/2005/09/msg00002.html"
name="a mail of Anthony Towns"> and
<url
id="http://wiki.debian.org/DebianScience/Sponsoring"
@@ -38,8 +38,7 @@
usertag <bug number> + wnpp <metapackage name>
</example>,
where email is the electronic address of the person or mailing
- list which coordinates the relevant Custom Debian
- Distribution.
+ list which coordinates the relevant Debian Pure Blend.
</p>
<p>
For instance if you want to tag an ITP with bug number
@@ -56,8 +55,8 @@
please always use lower case tags!
</p>
</item>
- <item>To search for WNPP bugs of a certain Custom Debian
- Distribution just visit the URL
+ <item>To search for WNPP bugs of a certain Debian Pure Blend just
+ visit the URL
<example>
http://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=wnpp;users=<var>email</var>
</example>
@@ -103,7 +102,7 @@
sgml-always-quote-attributes:t
sgml-indent-step:2
sgml-indent-data:t
-sgml-parent-document:("../debian-dis.en.sgml" "book" "chapt")
+sgml-parent-document:("../debian-blends.en.sgml" "book" "chapt")
sgml-exposed-tags:nil
sgml-local-catalogs:nil
sgml-local-ecat-files:nil
Modified: blends/trunk/docs/talks/200811_dresden/blends.tex
==============================================================================
--- blends/trunk/docs/talks/200811_dresden/blends.tex (original)
+++ blends/trunk/docs/talks/200811_dresden/blends.tex Sun Nov 9 08:22:05 2008
@@ -12,6 +12,7 @@
\usepackage{debian-at,debian-freebeer}
\usepackage[utf8]{inputenc}
+\usepackage{german}
\title{Debian Pure Blends}
@@ -22,7 +23,7 @@
%\institute{\Debian}
\institute{\link{http://www.linux-info-tag.de/100/detail/153}{Linux-Info-Tag}}
-\date{Dresden, 8. Oktober 2008}
+\date{Dresden, 8. November 2008}
% New definition of varcolor
\definecolor{VarColor}{rgb}{0,0,1} %
@@ -161,9 +162,9 @@
\begin{frame}
\frametitle{\package{blends-dev}}
\begin{itemize}
- \item Sicherstellen der Verfügbarkeit von \fix{Depends} / \fix{Recommends}
- \item Umwandeln von \fix{Depends} in \fix{Recommends}
- \item Pakete, die nicht in \dist{main} sind werden \fix{Suggests}
+ \item Sicherstellen der Verfügbarkeit von \fix{\large Depends} / \fix{\large Recommends}
+ \item Umwandeln von \fix{\large Depends} in \fix{\large Recommends}
+ \item Pakete, die nicht in \dist{main} sind werden \fix{\large Suggests}
\item Erzeuge geeignetes \file{debian/control} Datei korrekte
Metapakete zu erzeugen
\item Erzeuge \file{tasksel} Kontrolldatei \file{<Blend>-tasks.desc}
More information about the Cdd-commits
mailing list