r1806 - in trunk/website: . ant

Thu Jan 26 10:40:43 UTC 2006

Author: sgybas
Date: 2006-01-26 10:40:40 +0000 (Thu, 26 Jan 2006)
New Revision: 1806

Modified:
   trunk/website/ant/FOOTER.inc.html
   trunk/website/building.html
   trunk/website/developers.html
   trunk/website/index.html
Log:
Refer to the SVN repository instead of the old CVS repository


Modified: trunk/website/ant/FOOTER.inc.html
===================================================================

--- trunk/website/ant/FOOTER.inc.html	2006-01-26 10:20:14 UTC (rev 1805)
+++ trunk/website/ant/FOOTER.inc.html	2006-01-26 10:40:40 UTC (rev 1806)
@@ -9,7 +9,7 @@
 
       <li><a href="http://bugs.debian.org/cgi-bin/pkgreport.cgi?maint=pkg-java-maintainers@lists.alioth.debian.org">bugs in pkg-java public packages</a></li>
 
-      <li><a href="http://cvs.alioth.debian.org/cgi-bin/cvsweb.cgi/?cvsroot=pkg-java">CVS repository</a></li>
+      <li><a href="http://svn.debian.org/wsvn/pkg-java">SVN repository</a></li>
 
       <li><a href="../building.html">Hints for packaging Java software in Debian</a></li>
     </ul>

Modified: trunk/website/building.html
===================================================================
--- trunk/website/building.html	2006-01-26 10:20:14 UTC (rev 1805)
+++ trunk/website/building.html	2006-01-26 10:40:40 UTC (rev 1806)
@@ -43,7 +43,7 @@
       
       <li>If you are using Ant you can put ant.properties in the debian directory, call Ant with "-propertyfile path/to/debian/ant.properties" and define build.compiler, compile.debug and compile.optimize there.</li>
 
-      <li>Try to use patches instead of direct modifications to upstream sources. This way you only need to keep the debian directory in the CVS repository. You can use <a href="http://packages.debian.org/dpatch">dpatch</a> if the upstream source consists of just one tarball or <a href="http://packages.debian.org/dbs">DBS</a> for more complicated cases. Both can be integrated with <a href="http://build-common.alioth.debian.org/">cdbs</a>.</li>
+      <li>Try to use patches instead of direct modifications to upstream sources. This way you only need to keep the debian directory in the SVN repository. You can use <a href="http://packages.debian.org/dpatch">dpatch</a> if the upstream source consists of just one tarball or <a href="http://packages.debian.org/dbs">DBS</a> for more complicated cases. Both can be integrated with <a href="http://build-common.alioth.debian.org/">cdbs</a>.</li>
 
       <li>To update to a new upstream version, try to apply the .diff.gz from the previous version on top of the unpacked source tree. You can use uupdate from <a href="http://packages.debian.org/devscripts">devscripts</a> to facilitate this.</li>
     </ul>

Modified: trunk/website/developers.html
===================================================================
--- trunk/website/developers.html	2006-01-26 10:20:14 UTC (rev 1805)
+++ trunk/website/developers.html	2006-01-26 10:40:40 UTC (rev 1806)
@@ -44,9 +44,9 @@
     <h2><a name="rules"></a>General rules</h2>
 
     <ul>
-      <li>If you don't have experience with packaging Java software, send a patch to the pkg-java-maintainers list first before committting your changes to the <a href="http://cvs.alioth.debian.org/cgi-bin/cvsweb.cgi/?cvsroot=pkg-java">CVS repository</a></li>
+      <li>If you don't have experience with packaging Java software, send a patch to the pkg-java-maintainers list first before committting your changes to the <a href="http://svn.debian.org/wsvn/pkg-java">SVN repository</a>.</li>
 
-      <li><b>Test your changes</b> before committing to the CVS repository, i.e. make sure that the package can still be built. Also test if the package can be upgraded, purged and installed before uploading to the Debian archive.</li>
+      <li><b>Test your changes</b> before committing to the SVN repository, i.e. make sure that the package can still be built. Also test if the package can be upgraded, purged and installed before uploading to the Debian archive.</li>
 
       <li>Make sure that the package complies with the <a href="http://www.debian.org/doc/packaging-manuals/java-policy/">Java policy</a> (and the <a href="http://www.debian.org/doc/debian-policy/">Debian Policy</a>, of course). There are also some <a href="building.html">hints</a> for packaging Java software in Debian.</li>
 
@@ -60,12 +60,12 @@
     </ul>
     <hr>
 
-    <h2><a name="cvs">CVS repository</a></h2>
+    <h2><a name="svn">SVN repository</a></h2>
 
     <ul>
-      <li><b>Only commit modified files</b> (from *.diff.gz) to the CVS repository, <b>not the whole source tree</b>! You can use the <a href="http://cvs.alioth.debian.org/cgi-bin/cvsweb.cgi/importdiff.sh?cvsroot=pkg-java">importdiff.sh</a>script for this, don't use cvs-buildpackage!</li>
+      <li><b>Only commit modified files</b> (from *.diff.gz) to the SVN repository, <b>not the whole source tree</b>!</li>
 
-      <li><b>Tag uploaded package</b> versions with RELEASE_X_Y-Z for Debian version X.Y-Z<br>
+      <li><b>Tag uploaded package</b> versions in tags/<i>package name</i>/RELEASE_X_Y-Z for Debian version X.Y-Z<br>
       </li>
     </ul>
     <hr>

Modified: trunk/website/index.html
===================================================================
--- trunk/website/index.html	2006-01-26 10:20:14 UTC (rev 1805)
+++ trunk/website/index.html	2006-01-26 10:40:40 UTC (rev 1806)
@@ -50,7 +50,7 @@
 
       <li><a href="http://bugs.debian.org/cgi-bin/pkgreport.cgi?maint=pkg-java-maintainers@lists.alioth.debian.org">bugs in pkg-java public packages</a></li>
 
-      <li><a href="http://cvs.alioth.debian.org/cgi-bin/cvsweb.cgi/?cvsroot=pkg-java">pkg-java CVS repository</a></li>
+      <li><a href="http://svn.debian.org/wsvn/pkg-java">pkg-java SVN repository</a> (the old CVS repository is no longer used)</li>
 
       <li><a href="building.html">Hints for packaging Java software in Debian</a></li>
 


