Author: plessy
Date: 2011-03-21 08:39:33 +0000 (Mon, 21 Mar 2011)
New Revision: 6331

Modified:
   trunk/community/website/docs/policy.xml
Log:
Moved SVN build tips from Policy to new SVN tips section.


Modified: trunk/community/website/docs/policy.xml
===================================================================
--- trunk/community/website/docs/policy.xml     2011-03-21 08:22:27 UTC (rev 
6330)
+++ trunk/community/website/docs/policy.xml     2011-03-21 08:39:33 UTC (rev 
6331)
@@ -190,6 +190,32 @@
                        the <filename>trunk</filename>, 
<filename>tags</filename> and
                        <filename>branches</filename> directories are grouped 
together, so that developers can checkout trunks without tags.</para></note>
                </sect2>
+               <sect2 id="subversion-tips">
+                       <title>Subversion tips</title>
+                       <para>
+                               Suggested aliases for
+                               
<command>svn-buildpackage</command>:<programlisting>
+alias <command>svn-b</command>='svn-buildpackage -us -uc -rfakeroot 
--svn-ignore'
+alias <command>svn-br</command>='svn-b --svn-dont-purge --svn-reuse'
+alias <command>svn-bt</command>='svn-buildpackage --svn-tag 
-rfakeroot'</programlisting>
+                       </para>
+                       <para>
+                               To download the upstream sources (if there is a
+                               <filename>debian/watch</filename> file): 
<code><command>echo
+                               "origDir=.." &gt;&gt; .svn/deb-layout 
&amp;&amp; uscan
+                               --force-download</command></code>. 
Alternatively, you can try
+                               <code><command>debian/rules 
get-orig-source</command></code>.
+                       </para>
+                       <para>
+                               If you're a Debian developer or a member of the 
Debian Med group on
+                               Alioth, you can commit your changes: 
<command>svn commit</command> (also
+                               <command>svn ci</command>).  Otherwise, you can 
ask to be added to the
+                               group (see the <link 
linkend="membership">Membership</link> section), or
+                               send the result of <command>svn diff</command> 
to the <ulink
+                               
url="mailto:[email protected]";>mailing list</ulink>
+                               (<command>gzip -9</command> it, if it's too 
large).
+                       </para>
+               </sect2>
                <sect2 id="git-repository-structures">
                        <title>Common Git repository structures</title>
                        <para>
@@ -543,46 +569,6 @@
                <title>Building and tagging the packages</title>
             <sect3 id="building">
                        <title>Building the packages</title>
-            <sect4 id="building-subversion">
-            <title>Subversion</title>
-                       <para>To build the package, just use the tools that 
<command>svn-buildpackage</command>
-                       carries. First of all, we suggest you to define some 
aliases for the
-                       most common commands:</para>
-                       <blockquote>
-                               <programlisting>alias svn-b='svn-buildpackage 
-us -uc -rfakeroot --svn-ignore'
-alias svn-br='svn-b --svn-dont-purge --svn-reuse'
-alias svn-bt='svn-buildpackage --svn-tag -rfakeroot'</programlisting>
-                       </blockquote>
-                       <para>Checkout the sources (see the proper 
section).</para>
-                       <para>Once done, you're ready to do the work. First, cd 
to the trunk
-                       directory, and download the upstream sources (if there 
is a
-                       <filename>debian/watch</filename> file):</para>
-                       <blockquote>
-                               <para><userinput>
-                                       <command>echo "origDir=.." &gt;&gt; 
.svn/deb-layout &amp;&amp; uscan --force-download</command>
-                               </userinput></para>
-                       </blockquote>
-                       <para>Alternatively, you can try this, it depends on 
how the package
-                       was built (again, from the <filename 
class="directory">trunk/</filename> directory):</para>
-                       <blockquote>
-                               <para><userinput>
-                                       <command>debian/rules 
get-orig-source</command>
-                               </userinput></para>
-                       </blockquote>
-                       <para>Once done, edit the files you need, and then 
build the package with
-                       <command>svn-b</command> or 
<command>svn-br</command>.</para>
-                       <para>If you're a Debian Med member, you can commit 
your changes:</para>
-                       <blockquote>
-                               <para><userinput>
-                                       <command>svn commit</command>
-                               </userinput></para>
-                       </blockquote>
-                       <para>(also <command>svn ci</command>).</para>
-                       <para>Otherwise, you can ask to be added to the group 
(see the Membership
-                       section), or send the result of svn diff to the
-                       <ulink url="mailto:[email protected]";>mailing 
list</ulink>
-                       (<command>gzip -9</command> it, if it's too 
large).</para>
-            </sect4>
             <sect4 id="building-git">
                 <title>Git</title>
                 <para>You should use <command>git-buildpackage</command> to 
build the


_______________________________________________
debian-med-commit mailing list
[email protected]
http://lists.alioth.debian.org/mailman/listinfo/debian-med-commit

Reply via email to