[Blends-commit] r2437 - in /blends/trunk/blends/doc/docbook-xml/en: 00_titletoc.xml 02_about.xml 03_general_ideas.xml 06_technology.xml 08_websentinel.xml 09_todo.xml A_devel.xml B_quickintro.xml C_bts.xml
tille at users.alioth.debian.org
tille at users.alioth.debian.org
Wed Nov 10 13:58:45 UTC 2010
Author: tille
Date: Wed Nov 10 13:58:42 2010
New Revision: 2437
URL: http://svn.debian.org/wsvn/blends/?sc=1&rev=2437
Log:
fixed some syntactical errors in english doc by just using comments for unknown tags like <package>, <filename> etc. - better replacements should be found to get a logical markup somehow
Modified:
blends/trunk/blends/doc/docbook-xml/en/00_titletoc.xml
blends/trunk/blends/doc/docbook-xml/en/02_about.xml
blends/trunk/blends/doc/docbook-xml/en/03_general_ideas.xml
blends/trunk/blends/doc/docbook-xml/en/06_technology.xml
blends/trunk/blends/doc/docbook-xml/en/08_websentinel.xml
blends/trunk/blends/doc/docbook-xml/en/09_todo.xml
blends/trunk/blends/doc/docbook-xml/en/A_devel.xml
blends/trunk/blends/doc/docbook-xml/en/B_quickintro.xml
blends/trunk/blends/doc/docbook-xml/en/C_bts.xml
Modified: blends/trunk/blends/doc/docbook-xml/en/00_titletoc.xml
URL: http://svn.debian.org/wsvn/blends/blends/trunk/blends/doc/docbook-xml/en/00_titletoc.xml?rev=2437&op=diff
==============================================================================
--- blends/trunk/blends/doc/docbook-xml/en/00_titletoc.xml (original)
+++ blends/trunk/blends/doc/docbook-xml/en/00_titletoc.xml Wed Nov 10 13:58:42 2010
@@ -70,7 +70,7 @@
in the Subversion repository at
<citerefentry><refentrytitle>svn.debian.org</refentrytitle></citerefentry>
</ulink>.
- It is also available as Debian package <package>blends-doc</package>.
+ It is also available as Debian package <!--package-->blends-doc<!--/package-->.
</para>
<para>
Modified: blends/trunk/blends/doc/docbook-xml/en/02_about.xml
URL: http://svn.debian.org/wsvn/blends/blends/trunk/blends/doc/docbook-xml/en/02_about.xml?rev=2437&op=diff
==============================================================================
--- blends/trunk/blends/doc/docbook-xml/en/02_about.xml (original)
+++ blends/trunk/blends/doc/docbook-xml/en/02_about.xml Wed Nov 10 13:58:42 2010
@@ -76,9 +76,9 @@
<para>
<emphasis>Policy statements</emphasis> in this sense are things like
"configuration files live in
- <filename>/etc/$package/$package.conf</filename>, logfiles go to
- <filename>/var/log/$package/$package.log</filename> and the documentation
- files can be found in <filename>/usr/share/doc/$package</filename>."
+ <!--filename-->/etc/$package/$package.conf<!--/filename-->, logfiles go to
+ <!--filename-->/var/log/$package/$package.log<!--/filename--> and the documentation
+ files can be found in <!--filename-->/usr/share/doc/$package<!--/filename-->."
</para>
<para>
The policy statements are followed by the tool-chains and
@@ -91,8 +91,8 @@
It is this <emphasis>adherence to policy</emphasis> that causes a distribution
to remain consistent within its own bounds. At the same time, this is
the reason why packages can not always be safely installed across
- distribution boundaries. A SuSE <filename>package.rpm</filename> might not
- play well with a RedHat <filename>package.rpm</filename>, although the
+ distribution boundaries. A SuSE <!--filename-->package.rpm<!--/filename--> might not
+ play well with a RedHat <!--filename-->package.rpm<!--/filename-->, although the
packages work perfectly well within their own distributions. A
similar compatability problem could also apply to packages from the
same distributor, but from a different version or generation of the
@@ -197,7 +197,7 @@
how does the user find out which packages are really interesting?
</para>
<para>
-One solution is provided by the <package>tasksel</package> package.
+One solution is provided by the <!--package-->tasksel<!--/package--> package.
It provides a reasonable selection of quite general tasks that can be
accomplished using a set of packages installed on a Debian GNU/Linux
system. But this is not really fine grained, and does not address all
Modified: blends/trunk/blends/doc/docbook-xml/en/03_general_ideas.xml
URL: http://svn.debian.org/wsvn/blends/blends/trunk/blends/doc/docbook-xml/en/03_general_ideas.xml?rev=2437&op=diff
==============================================================================
--- blends/trunk/blends/doc/docbook-xml/en/03_general_ideas.xml (original)
+++ blends/trunk/blends/doc/docbook-xml/en/03_general_ideas.xml Wed Nov 10 13:58:42 2010
@@ -327,9 +327,9 @@
pool system was implemented to cope with the increased number of
packages while trying to reduce the time span between releases. Even
if the plan to increase the frequencies of releases failed Debian
- became a new quality. People started using the <filename>testing</filename>
+ became a new quality. People started using the <!--filename-->testing<!--/filename-->
distribution even in production which was not really intended and in
- a consequence even security in <filename>testing</filename> was implemented
+ a consequence even security in <!--filename-->testing<!--/filename--> was implemented
for Sarge.
</para>
<para>
Modified: blends/trunk/blends/doc/docbook-xml/en/06_technology.xml
URL: http://svn.debian.org/wsvn/blends/blends/trunk/blends/doc/docbook-xml/en/06_technology.xml?rev=2437&op=diff
==============================================================================
--- blends/trunk/blends/doc/docbook-xml/en/06_technology.xml (original)
+++ blends/trunk/blends/doc/docbook-xml/en/06_technology.xml Wed Nov 10 13:58:42 2010
@@ -40,7 +40,7 @@
</para></listitem>
<listitem><para>Menu entries (recommended)
<itemizedlist>
- <listitem><para>Place these in <filename>/etc/blends/<varname><blend></varname>/menu/<varname><pkg-name></varname></filename></para></listitem>
+ <listitem><para>Place these in <!--filename-->/etc/blends/<varname><blend></varname>/menu/<varname><pkg-name></varname><!--/filename--></para></listitem>
<listitem><para>Maintain these via role based tools</para></listitem>
</itemizedlist>
</para></listitem>
@@ -52,9 +52,9 @@
</para></listitem>
<listitem><para>Special metapackages:
<itemizedlist>
- <listitem><para><package><replaceable><blend></replaceable>-tasks</package>:
+ <listitem><para><!--package--><replaceable><blend></replaceable>-tasks<!--/package-->:
Contains information for <command>tasksel</command></para></listitem>
- <listitem><para><package><replaceable><blend></replaceable>-config</package>:
+ <listitem><para><!--package--><replaceable><blend></replaceable>-config<!--/package-->:
Special configurations, basic stuff for user menus</para></listitem>
</itemizedlist>
</para></listitem>
@@ -66,8 +66,8 @@
packages. The naming of metapackages follows the pattern
<varname><blend></varname>-<varname><task></varname>
where <varname><blend></varname> 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,
+Pure Blend, e.g. <!--package-->junior<!--/package--> for Debian
+Jr. or <!--package-->med<!--/package--> for Debian Med,
and <varname><task></varname> means the certain task inside the Blend,
e.g. puzzle or bio.
</para>
@@ -75,15 +75,15 @@
Examples:
<variablelist>
<varlistentry>
- <term><package>junior-puzzle</package></term>
+ <term><!--package-->junior-puzzle<!--/package--></term>
<listitem><para>Debian Jr. Puzzles</para></listitem>
</varlistentry>
<varlistentry>
- <term><package>education-tasks</package></term>
+ <term><!--package-->education-tasks<!--/package--></term>
<listitem><para>Tasksel files for SkoleLinux systems</para></listitem>
</varlistentry>
<varlistentry>
- <term><package>med-bio</package></term>
+ <term><!--package-->med-bio<!--/package--></term>
<listitem><para>Debian Med micro-biology packages</para></listitem>
</varlistentry>
</variablelist>
@@ -129,9 +129,9 @@
<title>Packages showing up in more than one metapackage</title>
<para>
-This seems to be an FAQ: If a package <package>A</package> is in the list of
-dependencies of metapackage <package>m</package> is it allowed or reasonable to
-add it to the list of dependencies of metapackage <package>n</package>?
+This seems to be an FAQ: If a package <!--package-->A<!--/package--> is in the list of
+dependencies of metapackage <!--package-->m<!--/package--> is it allowed or reasonable to
+add it to the list of dependencies of metapackage <!--package-->n<!--/package-->?
</para>
<para>
The answer is: Why not?
@@ -140,8 +140,8 @@
The "overlap" is no problem because we do not want to build
an exclusive categorisation which might be hard to understand for our
users. Metapackages are like "normal" packages: Nobody
-would assume that because package <package>x</package> depends from package
-<package>libc</package> no other package is allowed to add <package>libc</package> to its
+would assume that because package <!--package-->x<!--/package--> depends from package
+<!--package-->libc<!--/package--> no other package is allowed to add <!--package-->libc<!--/package--> to its
depends. So why not adding a dependency to more than one metapackage if
it is just useful for a certain task?
</para>
@@ -197,7 +197,7 @@
A "traditional" weakness of Free Software projects is missing
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
+can be done by building <!--package-->*-doc<!--/package--> packages of existing
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
@@ -245,7 +245,7 @@
The program <command>apt-cache</command> 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
- "<package>med</package>") and combine it reasonably with <command>grep</command>:
+ "<!--package-->med<!--/package-->") and combine it reasonably with <command>grep</command>:
<programlisting language="sh">
<![CDATA[
~> apt-cache search med | grep '^med-'
@@ -258,7 +258,7 @@
med-common - Debian Med Project common package
med-cms - Debian Med content management systems
]]>
- </programlisting>
+ <!--/programlisting-->
This is <emphasis role="strong">not really straightforward</emphasis>, and
absolutely unacceptable for end users.
</para></listitem>
@@ -306,7 +306,7 @@
Depends: clustalw | clustalw-mpi, clustalx, molphy, phylip, ...
Description: Debian Med micro-biology packages (contrib and ...
]]>
- </programlisting>
+ <!--/programlisting-->
This is, like the <command>apt-cache</command> example, <emphasis role="strong">also
a bit cryptic</emphasis>, and again is not acceptable for end users.
</para></listitem>
@@ -362,7 +362,7 @@
On Debian systems, the GPL can be found at /usr/share/common-...
/usr/share/doc/med-bio/copyright
]]>
- </programlisting>
+ <!--/programlisting-->
Just do your normal business - in the above example, <command>less
/usr/share/doc/med-bio/copyright</command> - and if the necessary
package is not yet installed, <command>auto-apt</command> will care for
@@ -404,7 +404,7 @@
</para>
<para>
As a workaround for this problem the <command>blends-dev</command>
- framework creates a package <package>BLEND-tasks</package> which contains
+ framework creates a package <!--package-->BLEND-tasks<!--/package--> which contains
a <command>tasksel</command> control file. If you install this package
all tasks of the Blend will be added to the default list of tasks
inside <command>tasksel</command>. So a solution for Blend specific
@@ -442,7 +442,7 @@
<term><command>gnome-apt</command></term>
<listitem><para>This is the native GNOME flavour of graphical user interfaces
to apt. It has a nice <command>Search</command> feature that can be
- found in the <package>Package</package> menu section. If for instance
+ found in the <!--package-->Package<!--/package--> menu section. If for instance
the packages of the Debian Jr. project come into the focus of
interest a search for "<varname>junior-*</varname>" will show
up all related packages including their descriptions. This
@@ -532,17 +532,17 @@
<para>These bugs pages are available via
<programlisting language="sh">
http://blends.alioth.debian.org/BLEND/bugs
- </programlisting>
+ <!--/programlisting-->
where <varname>BLEND</varname> has to be replaced by the name of the
Blend. Currently these pages are available for the Blends:
<programlisting language="sh">
accessibility, edu, gis, junior, lex, science, debichem
- </programlisting>
+ <!--/programlisting-->
The bugs pages are available for Debian Med as well but for
historical reasons the URL for these pages is
<programlisting language="sh">
http://debian-med.alioth.debian.org/bugs
- </programlisting>
+ <!--/programlisting-->
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.
@@ -634,8 +634,8 @@
</varlistentry>
<varlistentry>
<term><command>list-junior.sh</command></term>
- <listitem><para>The package <package>junior-doc</package> contains a script
- <filename>/usr/share/doc/junior-doc/examples/scripts/list-junior.sh</filename>
+ <listitem><para>The package <!--package-->junior-doc<!--/package--> contains a script
+ <!--filename-->/usr/share/doc/junior-doc/examples/scripts/list-junior.sh<!--/filename-->
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
@@ -658,7 +658,7 @@
available yet. The user interfaces for <command>apt-get</command> have to be
enhanced drastically to make them easy enough to make them useful in
the hands of an end user. This might implicitly mean that we need
-some additional control fields in <package>dpkg</package> to implement
+some additional control fields in <!--package-->dpkg<!--/package--> to implement
reasonable functionality. The following items are target of future
development:
<itemizedlist>
@@ -704,7 +704,7 @@
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 <filename>/etc/group</filename> file in the appropriate group and gets a
+the <!--filename-->/etc/group<!--/filename--> file in the appropriate group and gets a
special user menu that is provided for exactly this group.
</para>
<para>
@@ -756,29 +756,29 @@
<citerefentry><refentrytitle>blend-update-menus</refentrytitle>
<manvolnum>8</manvolnum></citerefentry>
(see <xref linkend="blend-update-menus" />) script from
-<package>blends-common</package>. It has to be said that using
+<!--package-->blends-common<!--/package-->. It has to be said that using
<command>blend-update-menus</command> is not enough to change the menu of a
user. To accomplish this a call of the general
<command>update-menu</command> script for every single user of a Blend is
necessary if this is not done by the
-<filename>postinst</filename> script of a metapackage. This can easily been
+<!--filename-->postinst<!--/filename--> script of a metapackage. This can easily been
done if the configuration file of a Debian Pure Blend
-<filename>/etc/blends/<varname><blend></varname>/<varname><blend></varname>.conf</filename> contains the
+<!--filename-->/etc/blends/<varname><blend></varname>/<varname><blend></varname>.conf<!--/filename--> contains the
line
<programlisting language="sh">
<![CDATA[
UPDATEUSERMENU=yes
]]>
-</programlisting>
+<!--/programlisting-->
</para>
<para>
It is strongly suggested to use the
-package <package>blends-dev</package> to build metapackages of a
+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
-<filename>menu</filename> directory with the menu entries. Note, that the users
-<filename>${HOME}/.menu</filename> directory remains untouched.
+<!--filename-->menu<!--/filename--> directory with the menu entries. Note, that the users
+<!--filename-->${HOME}/.menu<!--/filename--> directory remains untouched.
</para>
</sect3>
@@ -786,11 +786,11 @@
<title>Managing Debian Pure Blend users with <command>debconf</command></title>
<para>
-Using <package>blends-dev</package> it is very easy to build a
-<varname>blend</varname><package>-config</package> package that contains
+Using <!--package-->blends-dev<!--/package--> it is very easy to build a
+<varname>blend</varname><!--package-->-config<!--/package--> package that contains
<command>debconf</command> scripts to configure system users who should
belong to the group of users of the Debian Pure Blend <varname>blend</varname>.
-For example see the <package>med-common</package> package.
+For example see the <!--package-->med-common<!--/package--> package.
<programlisting language="sh">
<![CDATA[
@@ -812,13 +812,13 @@
:-! Please specify the Debian Med users! 2 8
]]>
- </programlisting>
+ <!--/programlisting-->
This example shows the situation when you
-<command>dpkg-reconfigure</command> <package>med-common</package> if
+<command>dpkg-reconfigure</command> <!--package-->med-common<!--/package--> if
<varname>med user B</varname> and <varname>med user H</varname> were defined as users
of Debian Med previously and <varname>med user F</varname> should be added to
the group of medical staff. (For sure it is more convenient to use the
-more comfortable interfaces to <package>debconf</package> but the used
+more comfortable interfaces to <!--package-->debconf<!--/package--> but the used
SGML DTD <ulink url="http://bugs.debian.org/140684" >does not yet
support screen shots</ulink>.)
</para>
@@ -832,10 +832,10 @@
<para>
Building a metapackage is more or less equal for each meta
package. This was the reason to build a common source package
-<package>blend</package> that builds into two binary packages
+<!--package-->blend<!--/package--> that builds into two binary packages
<variablelist>
<varlistentry>
- <term><package>blends-dev</package></term>
+ <term><!--package-->blends-dev<!--/package--></term>
<listitem><para>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
@@ -846,11 +846,11 @@
</para></listitem>
</varlistentry>
<varlistentry>
- <term><package>blends-common</package></term>
+ <term><!--package-->blends-common<!--/package--></term>
<listitem><para>This package provides some files that are common to meta
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
+ <!--package-->blends-dev<!--/package-->. It introduces a method to handle
system users in a group named according to the name of the
Blend. The user menu approach is explained in detail
in <xref linkend="userroles" />.</para>
Modified: blends/trunk/blends/doc/docbook-xml/en/08_websentinel.xml
URL: http://svn.debian.org/wsvn/blends/blends/trunk/blends/doc/docbook-xml/en/08_websentinel.xml?rev=2437&op=diff
==============================================================================
--- blends/trunk/blends/doc/docbook-xml/en/08_websentinel.xml (original)
+++ blends/trunk/blends/doc/docbook-xml/en/08_websentinel.xml Wed Nov 10 13:58:42 2010
@@ -23,11 +23,11 @@
according to recent developments of the Blend. The build process works
as follows:
<itemizedlist>
- <listitem><para>Read dependency information of the <filename>tasks</filename> files.</para></listitem>
+ <listitem><para>Read dependency information of the <!--filename-->tasks<!--/filename--> files.</para></listitem>
<listitem><para>Verify whether there is really a package with this name and
print the description of this package.</para></listitem>
<listitem><para>If there is no such package in Debian try to parse
- the <filename>tasks</filename> file whether there is some information
+ the <!--filename-->tasks<!--/filename--> file whether there is some information
given and mark the result as prospective package for further
inclusion.</para></listitem>
</itemizedlist>
@@ -122,8 +122,8 @@
can be addressed in this field. Unofficial packages which
have this field set are rendered in a separate section above
unofficial packages outside the official Debian mirrors.
- If you have set <filename>Vcs-Svn</filename> or <filename>Vcs-Git</filename>
- there is no need to set <filename>Vcs-Browser</filename> explicitely
+ If you have set <!--filename-->Vcs-Svn<!--/filename--> or <!--filename-->Vcs-Git<!--/filename-->
+ there is no need to set <!--filename-->Vcs-Browser<!--/filename--> explicitely
because it is obtained automatically from the other fields.
But you might override this automatically generated URL if
needed.
@@ -154,7 +154,7 @@
<varlistentry>
<term>Pkg-Description</term>
<listitem><para>This tag should give reasonable information about the
- software as it normally is done in <filename>debian/control</filename>
+ software as it normally is done in <!--filename-->debian/control<!--/filename-->
files. It can be either a copy of the description of the WNPP
bug or could be used to file a WNPP bug and thus helps to
simplify the packaging work.
@@ -268,7 +268,7 @@
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 <filename>tasks</filename> files are parsed for the listed
+page the <!--filename-->tasks<!--/filename--> files are parsed for the listed
dependencies. Then the Debian Bug Tracking System is consulted about
known bugs of these packages. All bugs are listed and marked with
different colours according to their severity. So the developers can
@@ -298,7 +298,7 @@
<para>
The Debian Quality Assurance group does a decent job in watching the
status o f Debian packages. If a package features a
-valid <filename>debian/watch</filename> the tool <command>uscan</command> is able to
+valid <!--filename-->debian/watch<!--/filename--> the tool <command>uscan</command> 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 Blend.
</para>
Modified: blends/trunk/blends/doc/docbook-xml/en/09_todo.xml
URL: http://svn.debian.org/wsvn/blends/blends/trunk/blends/doc/docbook-xml/en/09_todo.xml?rev=2437&op=diff
==============================================================================
--- blends/trunk/blends/doc/docbook-xml/en/09_todo.xml (original)
+++ blends/trunk/blends/doc/docbook-xml/en/09_todo.xml Wed Nov 10 13:58:42 2010
@@ -18,15 +18,15 @@
>Blends</ulink> on Alioth exists to organise the cooperation of developers.
The <ulink url="http://svn.debian.org/wsvn/blends/" >subversion repository</ulink>
can be browsed or checked out by by
-<programlisting>
+<!--programlisting-->
svn checkout svn://svn.debian.org/svn/blends blends
-</programlisting>
+<!--/programlisting-->
for anonymous users. Developers should check out via
-<programlisting>
+<!--programlisting-->
svn checkout svn+ssh://<varname>username</varname>@svn.debian.org/svn/blends blends
-</programlisting>
+<!--/programlisting-->
The current layout for the repository is as follows:
-<programlisting>
+<!--programlisting-->
blends -+- blends
| |
| +- tags -----+- cdd -+- 0.3 [older versions of cdd tools]
@@ -54,7 +54,7 @@
+- ...
|
...
-</programlisting>
+<!--/programlisting-->
There is
a <ulink url="http://lists.alioth.debian.org/mailman/listinfo/blends-commits"
>mailing list</ulink> with subversion changes and
@@ -237,9 +237,9 @@
found. Because these scripts are not configuration itself but
substantial part of a metapackage the suggestion would be to store
this stuff under
-<programlisting>
+<!--programlisting-->
/usr/share/blends/#BLEND#/#METAPACKAGE#/cf.#SOMETHING#
-</programlisting>
+<!--/programlisting-->
</para>
<para>
There was another suggestion at the Valencia workshop: Make use of
@@ -282,12 +282,12 @@
</para>
<para>
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>.
+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 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.
+<!--package-->blends-dev<!--/package--> version.
</para>
</sect1>
@@ -318,7 +318,7 @@
which leads to a <varname>stable</varname> subset release. The following graph
might clarify this:
-<programlisting>
+<!--programlisting-->
<![CDATA[
DD -> unstable --> testing --> stable
|
@@ -328,7 +328,7 @@
|
+---> ...
]]>
-</programlisting>
+<!--/programlisting-->
where <varname>BLEND_A</varname> / <varname>BLEND_B</varname> might be something like
<varname>debian-edu</varname> / <varname>debian-med</varname>. To implement this
@@ -378,7 +378,7 @@
obtained from the "releasable set" of testing (i.e. no
RC-bugs). This would make the structure above a little bit more flat:
-<programlisting>
+<!--programlisting-->
DD -> unstable --> testing --> releasable --> stable
|
+---> stable BLEND_A
@@ -386,12 +386,12 @@
+---> stable BLEND_B
|
+---> ...
-</programlisting>
+<!--/programlisting-->
A third suggestion was given at Congreso Software Libre Comunidad
Valenciana:
-<programlisting>
+<!--programlisting-->
testing_proposed_updated
|
|
@@ -403,7 +403,7 @@
+---> stable BLEND_B
|
+---> ...
-</programlisting>
+<!--/programlisting-->
The rationale behind these testing backports is that sometimes a
Debian Pure Blend is able to reduce the set of releasable
@@ -426,7 +426,7 @@
range of Debian packages. This would lead to a new layout of the file
structures of the Debian mirrors:
-<programlisting>
+<!--programlisting-->
debian/dists/stable/binary-i386
/binary-sparc
/binary-...
@@ -442,7 +442,7 @@
pool/main
/contrib
/non-free
-</programlisting>
+<!--/programlisting-->
To avoid flooding the archive with unnecessarily many versions of
packages for each single Debian Pure Blend a common base of all these
Blends has to be defined. Here some LSB conformance statement comes
@@ -452,7 +452,7 @@
<para>
Regarding to security issues there are two ways: Either one Debian
Pure Blend goes with the current stable Debian and thus the
-<filename>Packages.gz</filename> is just pointing to the very same versions
+<!--filename-->Packages.gz<!--/filename--> 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
Modified: blends/trunk/blends/doc/docbook-xml/en/A_devel.xml
URL: http://svn.debian.org/wsvn/blends/blends/trunk/blends/doc/docbook-xml/en/A_devel.xml?rev=2437&op=diff
==============================================================================
--- blends/trunk/blends/doc/docbook-xml/en/A_devel.xml (original)
+++ blends/trunk/blends/doc/docbook-xml/en/A_devel.xml Wed Nov 10 13:58:42 2010
@@ -1,41 +1,41 @@
<appendix id="DevelDescription">
<title>Description of development tools</title>
<sect1 id="blends-dev">
- <title>Package <package>blends-dev</package></title>
+ <title>Package <!--package-->blends-dev<!--/package--></title>
<para>
If metapackages are builded using the tools inside the
-<package>blends-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>blends-common</package> package. The goal is to keep
+<!--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
+<!--package-->blends<!--/package--> source package changes. Thus it is
strongly recommended to use the tools described below.
</para>
<para>
-The usage of the tools in the <package>blends-dev</package> package might
+The usage of the tools in the <!--package-->blends-dev<!--/package--> package might
introduce a versioned dependency in the
-<package><blend>-config</package> package from which
+<!--package--><blend>-config<!--/package--> package from which
all other metapackages of the <varname>Blend</varname> in question will
-depend. This <package><blend>-config</package> package
+depend. This <!--package--><blend>-config<!--/package--> package
instantiates the <varname>Blend</varname> in the common registry for all Blends in
-<filename>/etc/blends</filename>.
+<!--filename-->/etc/blends<!--/filename-->.
</para>
<para>
The best idea to use the tools provided by the
-<package>blends-dev</package> is to put a <filename>Makefile</filename> into the
+<!--package-->blends-dev<!--/package--> is to put a <!--filename-->Makefile<!--/filename--> into the
build directory containig one single line
-<programlisting>
+<!--programlisting-->
include /usr/share/blends-dev/Makefile
-</programlisting>
-
-(see <filename>/usr/share/doc/blends-dev/examples/Makefile</filename>). Using
-this <filename>Makefile</filename> all tools that were contained in
-<package>blends-dev</package> package versions before 0.4. These tools
-are moved to <filename>/usr/share/blends-dev/</filename> because there is no need
-to call them directly. Here is a list of the <filename>make</filename> targets.
+<!--/programlisting-->
+
+(see <!--filename-->/usr/share/doc/blends-dev/examples/Makefile<!--/filename-->). Using
+this <!--filename-->Makefile<!--/filename--> all tools that were contained in
+<!--package-->blends-dev<!--/package--> package versions before 0.4. These tools
+are moved to <!--filename-->/usr/share/blends-dev/<!--/filename--> because there is no need
+to call them directly. Here is a list of the <!--filename-->make<!--/filename--> targets.
</para>
<sect2 id="blends-tasks.desc">
@@ -45,8 +45,8 @@
This target is the description file that is used in
<command>tasksel</command> to enable selecting the tasks belonging to the
Blend. The file will be moved to the
-<varname>blend</varname><package>-tasks</package>. All information is obtained
-from the single task files in the <filename>tasks</filename> directory of the
+<varname>blend</varname><!--package-->-tasks<!--/package-->. All information is obtained
+from the single task files in the <!--filename-->tasks<!--/filename--> directory of the
Blend source.
</para>
@@ -55,16 +55,16 @@
<title><varname>debian/control</varname></title>
<para>
-The <filename>debian/control</filename> file of a Blend metapackage source
+The <!--filename-->debian/control<!--/filename--> file of a Blend metapackage source
archive is auto generated out of dependencies that are specified in so
-called <filename>tasks</filename> files. The rationale behind this is to
+called <!--filename-->tasks<!--/filename--> 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 <filename>tasks</filename> just define which dependencies the Blend
+The <!--filename-->tasks<!--/filename--> just define which dependencies the Blend
maintainer group wants to be fulfilled and the
script <command>blend-gen-control</command> verifies whether these
dependencies exist in the specified package pool and create
-the <filename>debian/control</filename> file according to the available
+the <!--filename-->debian/control<!--/filename--> file according to the available
packages. This does not only work for the Debian package pool
containing the distributions stable, testing and unstable. You can
even build your metapackages against a different package pool of a
@@ -72,19 +72,19 @@
SkoleLinux metapackages.
</para>
<para>
-The syntax of the <filename>tasks</filename> files which serve as the central
-database for the information in the <filename>debian/control</filename> file
+The syntax of the <!--filename-->tasks<!--/filename--> files which serve as the central
+database for the information in the <!--filename-->debian/control<!--/filename--> file
is defined by RFC822. Some of the tags were mentioned formerly in
-<xref linkend="packageslist" /> to explain how the <filename>tasks</filename> files
+<xref linkend="packageslist" /> to explain how the <!--filename-->tasks<!--/filename--> files
can be used to create the web sentinel pages. Now the tags that
-influence the creation of the <filename>debian/control</filename> file are given.
+influence the creation of the <!--filename-->debian/control<!--/filename--> file are given.
</para>
<para>
<variablelist>
<varlistentry>
<term>Depends</term>
<listitem><para>Will be turned to "Recommends" in the
- resulting <filename>debian/control</filename> file. The
+ resulting <!--filename-->debian/control<!--/filename--> file. The
rationale behind this is to enable installing the
metapackage even if a package belonging to this task is
missing for whatever reason. It also allows finally to
@@ -117,13 +117,13 @@
<para>
If a package is not available in the package pool of the
target distribution when creating
- the <filename>debian/control</filename> file inside the meta
+ the <!--filename-->debian/control<!--/filename--> file inside the meta
package source archive any "Depends" or "Recommends" are
turned into "Suggests" to enable a flawless installation
of the metapackage. Packages that are specified with
"Suggests" will not be taken over to
the <command>tasksel</command> control file
- (Blend<filename>-tasks.desk</filename>,
+ (Blend<!--filename-->-tasks.desk<!--/filename-->,
see <xref linkend="blends-tasks.desc" />) but only to the list of
suggested packages of the according metapackage.
</para></listitem>
@@ -134,8 +134,8 @@
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 <filename>debian/control</filename> file of the resulting
- metapackage neither to the Blend<filename>-tasks.desk</filename>
+ the <!--filename-->debian/control<!--/filename--> file of the resulting
+ metapackage neither to the Blend<!--filename-->-tasks.desk<!--/filename-->
control file for <command>tasksel</command> but will be taken
over onto the installation medium of a Blend in case there
is some space left. This key becomes especially
@@ -148,7 +148,7 @@
<varlistentry>
<term>Avoids</term>
<listitem><para>The "Avoids" key specifies existing packages that will
- be listed in the the <filename>debian/control</filename> file as
+ be listed in the the <!--filename-->debian/control<!--/filename--> file as
"Recommends" or "Suggests" but, should not go to a
installation medium (CD, DVD, etc.) that might be
produced by the Blend. A reason to avoid a package might
@@ -160,48 +160,48 @@
</sect2>
<sect2>
- <title>Apt <filename>sources.list</filename> files in <filename>/etc/blends/</filename></title>
+ <title>Apt <!--filename-->sources.list<!--/filename--> files in <!--filename-->/etc/blends/<!--/filename--></title>
<para>
These files are used by <citerefentry><refentrytitle>blend-gen-control</refentrytitle><manvolnum>1</manvolnum></citerefentry> to
-build valid <filename>debian/control</filename> files that contain only
+build valid <!--filename-->debian/control<!--/filename--> files that contain only
available packages in their dependencies. This enables building meta
packages for <varname>stable</varname>, <varname>testing</varname>, <varname>unstable</varname> or
even a completely different distribution that has valid
-<filename>sources.list</filename> entries. The file
-<filename>/etc/blends/control.list</filename> is used as default for
+<!--filename-->sources.list<!--/filename--> entries. The file
+<!--filename-->/etc/blends/control.list<!--/filename--> is used as default for
<citerefentry><refentrytitle>blend-gen-control</refentrytitle><manvolnum>1</manvolnum></citerefentry> and usually is a symbolic link
(see <citerefentry><refentrytitle>ln</refentrytitle><manvolnum>1</manvolnum></citerefentry>) to
-<filename>sources.list.</filename><varname>distribution</varname>. It might be
+<!--filename-->sources.list.<!--/filename--><varname>distribution</varname>. It might be
changed using the <varname>-s </varname><varname>dist</varname> option of <citerefentry><refentrytitle>blend-gen-control</refentrytitle><manvolnum>1</manvolnum></citerefentry>.
</para>
<para>
<emphasis role="strong">TODO:</emphasis> <emphasis>Either parse the available
-<filename>/etc/apt/sources.list</filename> or use a sane <command>debconf</command>
+<!--filename-->/etc/apt/sources.list<!--/filename--> or use a sane <command>debconf</command>
question to use the "nearest" mirror.</emphasis>
</para>
</sect2>
<sect2>
- <title>Templates in <filename>/usr/share/blends/templates</filename></title>
-<para>
-The directory <filename>/usr/share/blends/templates</filename> contains templates
-that can be used to build a <varname><blend></varname><package>-config</package>,
+ <title>Templates in <!--filename-->/usr/share/blends/templates<!--/filename--></title>
+<para>
+The directory <!--filename-->/usr/share/blends/templates<!--/filename--> contains templates
+that can be used to build a <varname><blend></varname><!--package-->-config<!--/package-->,
which uses the tools that are contained in the
-<package>blends-common</package> package, and are useful to manage
+<!--package-->blends-common<!--/package--> package, and are useful to manage
<varname><blend></varname> user groups (see <xref linkend="userroles" />).
</para>
</sect2>
</sect1>
<sect1 id="blends-common">
- <title>Package <package>blends-common</package></title>
+ <title>Package <!--package-->blends-common<!--/package--></title>
<para>
This package creates a common registry for all Blends in
-<filename>/etc/blends</filename>. Each Blend should put the files that are used
-into a subdirectory named like the Blend of <filename>/etc/blends</filename>. The
-<package>blends-common</package> package installs a common configuration
-file <filename>/etc/blends/blends.conf</filename>, which can be used to influence the
+<!--filename-->/etc/blends<!--/filename-->. Each Blend should put the files that are used
+into a subdirectory named like the Blend of <!--filename-->/etc/blends<!--/filename-->. The
+<!--package-->blends-common<!--/package--> package installs a common configuration
+file <!--filename-->/etc/blends/blends.conf<!--/filename-->, which can be used to influence the
behaviour of the tools described below.
</para>
@@ -386,17 +386,17 @@
<varlistentry>
<term>NAME</term>
<listitem><para>
- <filename>blends.conf</filename> - configuration for Debian Pure Blends registry
+ <!--filename-->blends.conf<!--/filename--> - configuration for Debian Pure Blends registry
</para></listitem>
</varlistentry>
<varlistentry>
<term>DESCRIPTION</term>
<listitem><para>This file is sourced from shell scripts inside the Debian
- Pure Blends package <package>blends-common</package> and thus
+ 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
- <filename>/etc/blends/<varname><Blend></varname>/<varname><Blend></varname>.conf</filename>
+ <!--filename-->/etc/blends/<varname><Blend></varname>/<varname><Blend></varname>.conf<!--/filename-->
for each single Blend.</para></listitem>
</varlistentry>
<varlistentry>
@@ -447,8 +447,8 @@
<varlistentry>
<term>SEE ALSO</term>
<listitem><para>
- <filename>blend-role (8)</filename>, <filename>blend-update-menus (8)</filename>,
- <filename>blend-user (8)</filename>
+ <!--filename-->blend-role (8)<!--/filename-->, <!--filename-->blend-update-menus (8)<!--/filename-->,
+ <!--filename-->blend-user (8)<!--/filename-->
</para></listitem>
</varlistentry>
<varlistentry>
@@ -464,45 +464,45 @@
<sect1 id="svn">
- <title>Working with <filename>svn</filename></title>
+ <title>Working with <!--filename-->svn<!--/filename--></title>
<para>
Sometimes it might be interesting for developers to check out the
latest code of the Blend tools or a special Blend code for the meta
packages. In <xref linkend="communication" /> the directory layout of the
- <filename>svn</filename>-directory was described. How to derive the
+ <!--filename-->svn<!--/filename-->-directory was described. How to derive the
Debian packages from this layout?
<variablelist>
<varlistentry>
<term>Checkout</term>
<listitem><para>
For the Blend tools
-<programlisting>
+<!--programlisting-->
svn checkout svn+ssh://<varname>username</varname>@svn.debian.org/svn/blends/blends/trunk/blends blends
-</programlisting>
+<!--/programlisting-->
or for the Debian Pure Blend <varname>BLEND-name</varname>
-<programlisting>
+<!--programlisting-->
svn checkout svn+ssh://<varname>username</varname>@svn.debian.org/svn/blends/projects/<varname>BLEND-name</varname>/trunk
-</programlisting>
+<!--/programlisting-->
</para></listitem>
</varlistentry>
<varlistentry>
<term>Build source package</term>
<listitem><para>
Change into the created directory and type
-<programlisting>
+<!--programlisting-->
make -f debian/rules get-orig-source
-</programlisting>
- This creates a <filename>tar.gz</filename> source archive of the packages
+<!--/programlisting-->
+ This creates a <!--filename-->tar.gz<!--/filename--> source archive of the packages
you want to build. For your personal comfort you can create a
- file <filename>Makefile</filename> in your package source directory containing
-<programlisting>
+ file <!--filename-->Makefile<!--/filename--> in your package source directory containing
+<!--programlisting-->
#!/usr/bin/make -f
include /usr/share/blends-dev/Makefile
-</programlisting>
+<!--/programlisting-->
Which enables you to simply say
-<programlisting>
+<!--programlisting-->
make dist
-</programlisting>
+<!--/programlisting-->
to create the source tarball.
</para></listitem>
</varlistentry>
Modified: blends/trunk/blends/doc/docbook-xml/en/B_quickintro.xml
URL: http://svn.debian.org/wsvn/blends/blends/trunk/blends/doc/docbook-xml/en/B_quickintro.xml?rev=2437&op=diff
==============================================================================
--- blends/trunk/blends/doc/docbook-xml/en/B_quickintro.xml (original)
+++ blends/trunk/blends/doc/docbook-xml/en/B_quickintro.xml Wed Nov 10 13:58:42 2010
@@ -21,12 +21,12 @@
<para>
This howto describes the building of metapackages by using the
-<package>blends-dev</package> package. It is perfectly possible to
+<!--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.
- <programlisting>
+ <!--programlisting-->
~> cp -a /usr/share/doc/blends-dev/examples/tasks .
~> cat tasks/README
~> edit tasks/task1
@@ -34,11 +34,11 @@
long description as in any debian/control file</varname>
Depends: <varname>dependency1, dependency2, ...</varname>
- </programlisting>
-
-For each metapackage this skeleton of a <filename>debian/control</filename>
+ <!--/programlisting-->
+
+For each metapackage this skeleton of a <!--filename-->debian/control<!--/filename-->
entry is needed. All necessary information is available in the
-directory <filename>/usr/share/doc/blends-dev/examples/tasks</filename>.
+directory <!--filename-->/usr/share/doc/blends-dev/examples/tasks<!--/filename-->.
</para>
</sect1>
@@ -47,60 +47,60 @@
<para>
To build any Debian package you always need a directory named
-<filename>debian</filename>, which contains a certain set of files. The
-package <package>blends-dev</package> provides a complete set of example
+<!--filename-->debian<!--/filename-->, which contains a certain set of files. The
+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.
-<programlisting>
+<!--programlisting-->
~> cp -a /usr/share/doc/blends-dev/examples/debian .
~> cat debian/README
~> edit debian/control.stub
-</programlisting>
-Now the variables in the file <filename>control.stub</filename> change the
+<!--/programlisting-->
+Now the variables in the file <!--filename-->control.stub<!--/filename--> change the
variables named <varname>_BLEND_</varname>, <varname>_MAINTAINER_</varname> etc. to
match the names of the Debian Pure Blend to be built. Please note
-that the file <filename>debian/control</filename> is and has to be a symbolic
-link to <filename>control.stub</filename> to let the
-<package>blends-dev</package> tools work.
-
-<programlisting>
+that the file <!--filename-->debian/control<!--/filename--> is and has to be a symbolic
+link to <!--filename-->control.stub<!--/filename--> to let the
+<!--package-->blends-dev<!--/package--> tools work.
+
+<!--programlisting-->
~> edit debian/rules
-</programlisting>
-
-Also in the <filename>debian/rules</filename> the name of the Blend has to be
+<!--/programlisting-->
+
+Also in the <!--filename-->debian/rules<!--/filename--> the name of the Blend has to be
inserted where the template contains
<varname>_BLEND_</varname>. Depending from the way the
-<filename>sources.list</filename> should be scanned the options for the
+<!--filename-->sources.list<!--/filename--> should be scanned the options for the
<command>gen-control</command> call can be adjusted.
</para>
<para>
You have to build the tarball using the command
-<programlisting>
+<!--programlisting-->
~> make -f debian/rules get-orig-source
-</programlisting>
+<!--/programlisting-->
For your comfort you might like to create a file
-<filename>Makefile</filename> containing
-<programlisting>
+<!--filename-->Makefile<!--/filename--> containing
+<!--programlisting-->
#!/usr/bin/make -f
include /usr/share/blends-dev/Makefile
-</programlisting>
+<!--/programlisting-->
which enables you to simply use
-<programlisting>
+<!--programlisting-->
~> make dist
-</programlisting>
+<!--/programlisting-->
to build the source tarball. This tarball has to be moved to a location
where the metapackages will be built.
Unpack the tarball there and start the build process
using for instance
-<programlisting>
+<!--programlisting-->
~> debuild
-</programlisting>
+<!--/programlisting-->
</para>
<para>
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>blends-dev</package> tools to support these menus.
+<!--package-->blends-dev<!--/package--> tools to support these menus.
</para>
</sect1>
@@ -112,26 +112,26 @@
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
-<filename>blend-install-helper</filename>, which is called in
-<filename>debian/rules</filename>, if the <filename>common</filename> directory exists.
+<!--filename-->blend-install-helper<!--/filename-->, which is called in
+<!--filename-->debian/rules<!--/filename-->, if the <!--filename-->common<!--/filename--> directory exists.
The easiest way to create this is as follows:
-<programlisting>
+<!--programlisting-->
~> cp -a /usr/share/doc/blends-dev/examples/common .
~> cat common/README
~> edit common/conf common/control common/common.1
-</programlisting>
+<!--/programlisting-->
The variables (<varname>_BLEND_</varname>) in these three files have to be
adjusted to the name of the Debian Pure Blend in question.
-This <filename><varname>blend</varname>-config</filename> cares for the initialisation
+This <!--filename--><varname>blend</varname>-config<!--/filename--> cares for the initialisation
of the role based menu system and might contain adjustments of the
-general configuration inside the <package>blends-common</package>.
-</para>
-<para>
-If the metapackage <package>blend-config</package> will be
+general configuration inside the <!--package-->blends-common<!--/package-->.
+</para>
+<para>
+If the metapackage <!--package-->blend-config<!--/package--> will be
created according to these rules all other metapackages will depend
automatically from this common package. For the friends of
<command>auto-apt</command>, a helper
-<filename>/usr/bin/<metapackage-name></filename> will be
+<!--filename-->/usr/bin/<metapackage-name><!--/filename--> will be
installed as well, which just prints some information about the meta
package. All in all, the usage of the common package is strongly
suggested to have a common registry for stuff like user roles and
@@ -144,16 +144,16 @@
<para>
As explained in <xref linkend="menu_tools" /> the metapackages can contain
user menus. This optional feature can be implemented easily by using
-the template from the <package>blends-dev</package> in the following way:
-
-<programlisting>
+the template from the <!--package-->blends-dev<!--/package--> in the following way:
+
+<!--programlisting-->
~> cp -a /usr/share/doc/blends-dev/examples/menu .
~> cat menu/README
~> edit menu/task1
<varname>Edit the example to legal menu entries of the
dependencies of this metapackage</varname>
~> cp menu/task1 menu/<varname><metapackage name></varname>
-</programlisting>
+<!--/programlisting-->
A menu file for each task should be created containing valid menu
entries for each dependant package. The easiest way to obtain those
@@ -161,8 +161,8 @@
contained in the packages on which the metapackage will depend.
The only thing that has to be changed in these menu entries is the
<varname>package</varname> field, which has to be changed from
-<package><dependent package></package> to
-<package>blend-task</package>. All other entries
+<!--package--><dependent package><!--/package--> to
+<!--package-->blend-task<!--/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").
@@ -172,11 +172,11 @@
</para>
<para>
In principle these menu items could be created automatically either at
-metapackage build time or even better in the <filename>postinst</filename>
+metapackage build time or even better in the <!--filename-->postinst<!--/filename-->
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>blends-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
@@ -199,7 +199,7 @@
creator of the metapackage. Such documentation can be created using
the following templates:
-<programlisting>
+<!--programlisting-->
~> cp -a /usr/share/doc/blends-dev/examples/docs .
~> cat docs/README
~> edit docs/task1/dep1
@@ -208,7 +208,7 @@
contain a useful menu entry.</varname>
~> cp docs/task1/dep1 docs/task1/<varname><dependent pkg></varname>
~> cp -a docs/task1 docs/<varname><metapackage name></varname>
-</programlisting>
+<!--/programlisting-->
This ensures that our users become aware of all interesting packages
on their system. The documentation files should contain hints to man
Modified: blends/trunk/blends/doc/docbook-xml/en/C_bts.xml
URL: http://svn.debian.org/wsvn/blends/blends/trunk/blends/doc/docbook-xml/en/C_bts.xml?rev=2437&op=diff
==============================================================================
--- blends/trunk/blends/doc/docbook-xml/en/C_bts.xml (original)
+++ blends/trunk/blends/doc/docbook-xml/en/C_bts.xml Wed Nov 10 13:58:42 2010
@@ -33,10 +33,10 @@
<listitem><para>
Add an usertag to an existing bug by sending to
request at bugs.debian.org a mail containing
- <programlisting>
+ <!--programlisting-->
user <email>
usertag <bug number> + wnpp <metapackage name>
- </programlisting>,
+ <!--/programlisting-->,
where email is the electronic address of the person or mailing
list which coordinates the relevant Debian Pure Blend.
</para>
@@ -44,11 +44,11 @@
For instance if you want to tag an ITP with bug number
#123456 for Debian Med section biology you would send the
following mail to <email>request at bugs.debian.org </email>:
- <programlisting>
+ <!--programlisting-->
user debian-med at lists.debian.org
usertag 123456 + wnpp med-bio
thanks
- </programlisting>
+ <!--/programlisting-->
</para>
<para>
<emphasis role="strong">Note:</emphasis> Because the search is case sensitive
@@ -57,9 +57,9 @@
</listitem>
<listitem><para>To search for WNPP bugs of a certain Debian Pure Blend just
visit the URL
-<programlisting>
+<!--programlisting-->
http://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=wnpp;users=<varname>email</varname>
-</programlisting>
+<!--/programlisting-->
</para></listitem>
</itemizedlist>
More information about the Blends-commit
mailing list