[Pkg-kde-commits] rev 1629 - www/docs/domi

[Luk Claes]

Author: luk
Date: 2005-09-01 13:30:06 +0000 (Thu, 01 Sep 2005)
New Revision: 1629

Modified:
   www/docs/domi/debian-kde-debug.html
   www/docs/domi/debugging-kde-crash.html
   www/docs/domi/packaging-kde-modules.html
Log:
Use html entities


Modified: www/docs/domi/debian-kde-debug.html
===================================================================
--- www/docs/domi/debian-kde-debug.html	2005-09-01 13:21:26 UTC (rev 1628)
+++ www/docs/domi/debian-kde-debug.html	2005-09-01 13:30:06 UTC (rev 1629)
@@ -18,7 +18,7 @@
     
       <pre>deb http://www.kde-debian.org/~domi/debian-kde-debug/ unstable main</pre>
     
-    After that, execute the command "apt-get update && apt-get
+    After that, execute the command "apt-get update &amp;&amp; apt-get
     upgrade" as root from a terminal.</p>
 
     <h2>Uninstalling</h2>

Modified: www/docs/domi/debugging-kde-crash.html
===================================================================
--- www/docs/domi/debugging-kde-crash.html	2005-09-01 13:21:26 UTC (rev 1628)
+++ www/docs/domi/debugging-kde-crash.html	2005-09-01 13:30:06 UTC (rev 1629)
@@ -58,7 +58,7 @@
     we need the argument.</p>
 
     <p>Next start the application in valgrind: <pre>valgrind kopete
-    --nofork > /tmp/valgrind-crash-output.txt 2>&1 </pre> Only use the
+    --nofork &gt; /tmp/valgrind-crash-output.txt 2&gt;&amp;1 </pre> Only use the
     --nofork argument if you need it ( see the above paragraph ), and
     replace "kopete" by the application that is crashing for
     you. Then, you need to trigger the crash in the application.

Modified: www/docs/domi/packaging-kde-modules.html
===================================================================
--- www/docs/domi/packaging-kde-modules.html	2005-09-01 13:21:26 UTC (rev 1628)
+++ www/docs/domi/packaging-kde-modules.html	2005-09-01 13:30:06 UTC (rev 1629)
@@ -71,11 +71,11 @@
     <pre>
 # export the modules
 echo &quot;Checking out $releasedir...&quot;
-cvs -d$CVSROOT export -r${release_tag} $MODULE > /dev/null
+cvs -d$CVSROOT export -r${release_tag} $MODULE &gt; /dev/null
 mv &quot;$MODULE&quot; &quot;$releasedir&quot;
 
 echo &quot;Checking out $branchdir...&quot;
-cvs -d$CVSROOT export -r${branch_tag} $MODULE > /dev/null
+cvs -d$CVSROOT export -r${branch_tag} $MODULE &gt; /dev/null
 mv &quot;$MODULE&quot; &quot;$branchdir&quot;
     </pre>
 
@@ -111,8 +111,8 @@
 
 # the branch diff
 temp=`tempfile`
-diff -Nrua &quot;$releasedir&quot; &quot;$branchdir&quot; > $temp
-cat $temp | uuencode 001-$MODULE-branch.diff > &quot;$branchdir/debian/patches/001-$MODULE-branch.diff.uu&quot;
+diff -Nrua &quot;$releasedir&quot; &quot;$branchdir&quot; &gt; $temp
+cat $temp | uuencode 001-$MODULE-branch.diff &gt; &quot;$branchdir/debian/patches/001-$MODULE-branch.diff.uu&quot;
 cd &quot;$branchdir&quot;
 # first unapply the branch patch, it will be reapplied by debian/rules
 # configure
@@ -155,7 +155,7 @@
 # is not built by the rules script ( by make -f admin/Makefile.common
 # ), and it is subsequently attempted to be run with a lot of args,
 # but it simply ignores them
-echo "echo 'this is a fake configure \!'" > configure
+echo "echo 'this is a fake configure \!'" &gt; configure
 chmod a+x configure
 make -f debian/rules configure
 rm -f configure-stamp