[Blends-commit] [SCM] blends-dev branch, master, updated. 36022b7d787a53f917a52f06fe844d0734e28111

[Andreas Tille]

The following commit has been merged in the master branch:
commit 36022b7d787a53f917a52f06fe844d0734e28111
Author: Andreas Tille <tille at debian.org>
Date:   Sat Jul 4 16:38:00 2015 +0200

    Drop Simple-CDD from docs ; document how to deal with name space pollution

diff --git a/debian/changelog b/debian/changelog
index edf6807..98a5878 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,10 @@
+blends (0.6.92.4) UNRELEASED; urgency=medium
+
+  * Drop Simple-CDD from docs
+  * Document how to deal with name space pollution
+
+ -- Andreas Tille <tille at debian.org>  Sat, 04 Jul 2015 16:37:24 +0200
+
 blends (0.6.92.3) unstable; urgency=medium
 
   * document that the task files follow RFC 822 format (thanks for the
diff --git a/doc/en/06_technology.xml b/doc/en/06_technology.xml
index 510952f..0848280 100644
--- a/doc/en/06_technology.xml
+++ b/doc/en/06_technology.xml
@@ -936,37 +936,62 @@ described now in detail.
 </para>
 
 </sect1>
-   <sect1 id="othertools">
-   <title>Other interesting tools</title>
-
-   <sect2 id="simple-cdd">
-   <title>Simple-CDD</title>
-
-<para>
-The tool <package>simple-cdd</package> is a limited though relatively easy
-tool to create a customized debian-installer CD.
-</para><para>
-It includes simple mechanisms to create "profiles" that define common
-system configurations, which can be selected during system
-installation. <package>Simple-cdd</package>  also makes it easy to build CDs
-with language and country settings pre-configured, or to use a 2.6
-kernel by default.
-</para><para>
-This can be used to create a crude "Debian Pure Blend" using
-packages from Debian, with pre-configuration of packages that use
-<orgname>debconf</orgname>.  Custom configuration scripts can be specified
-to handle packages that don't support <orgname>debconf</orgname>
-pre-configuration.
-</para><para>
-Testing CD images with <package>qemu</package> is also made simple with a
-provided script.
-</para><para>
-It has only been tested with <package>debian-cd</package> from Etch (other
-than <package>debpartial-mirror</package>), so if using a new
-<package>debian-cd</package> or <package>debian-installer</package>, it may
-require some tweaks.
+   <sect1 id="namespace">
+   <title>Dealing with name space pollution</title>
+
+<para>
+Due to the fact that Blends might deal with quite specialised software
+the user base is often quite small.  In such use cases it happens that
+some programs are using names that are used by other more frequently
+used tools.  For instance the Debian Med program <package>plink</package>
+has the same name as the program <filename>plink</filename> that belongs
+to the ssh clone <package>putty</package>.  According to the Debian policy
+both packages, <package>putty</package> and <package>plink</package> both
+packages need to be co-installable.  Thus one tool has to be renamed.
+</para>
+<para>
+Name space conflicts in Debian are usually solved by the principle that
+whoever comes first has taken the name if there is no better agreement.
+However, it makes sense to keep the original name choosen by upstream
+for the more frequently used program - and here it might be that the
+Blends packager steps back.  There might be a chance to discuss with
+upstream about a better name but there is no guarantee that this will be
+successfully and thus there is another option for the Blends developer
+to provide the original upstream name to the Blends users by circumventing
+the file name conflict - at least for users of the <filename>bash</filename>
+shell.
+</para>
+<para>
+Since <package>blends-dev >= 0.6.92.3</package> in the 
+<varname>blend</varname><package>-config</package> a <filename>bash</filename>
+init script is provided in
+</para>
+    <informalexample>
+      <programlisting>
+  /etc/profile.d/<varname><BLEND-name></varname>.sh
+      </programlisting>
+    </informalexample>
+<para>
+This script is executed in login shells and checks for two things:
+</para>
+<para>
+<orderedlist>
+  <listitem><para>
+    Does the path <filename>/usr/lib/<varname><BLEND-name></varname>/bin</filename>
+    exist (since a package installs files there)?
+  </para></listitem>
+  <listitem><para>
+    Has the user starting the <filename>bash</filename> instance created a file
+    <filename>$HOME/.blends</filename> and is there a line featuring the name
+    of the Blend (in the example above "debian-med")
+  </para></listitem>
+</orderedlist>
+</para>
+<para>
+If both conditions are fullfilled the PATH gets prependet by
+<filename>/usr/lib/<varname><BLEND-name></varname>/bin</filename>
+and thus the tools residing in this directory were found first.
 </para>
-   </sect2>
    </sect1>
 
 </chapter>

-- 
Git repository for blends code