[Pkg-octave-commit] rev 15 - trunk

Rafael Laboissiere rafael@costa.debian.org
Tue, 08 Feb 2005 09:57:26 +0100


Author: rafael
Date: 2005-02-08 09:57:26 +0100 (Tue, 08 Feb 2005)
New Revision: 15

Modified:
   trunk/README
Log:
Added real contents

Modified: trunk/README
===================================================================
--- trunk/README	2005-02-08 08:26:49 UTC (rev 14)
+++ trunk/README	2005-02-08 08:57:26 UTC (rev 15)
@@ -5,19 +5,29 @@
 1. Coordination
 ---------------
 
-Debian Group @ Alioth
-mailing list
-common maintenance 
-common build infrastructure
+The development of Octave-related packages in Debian is done as a
+collaborative work by the Debian Octave Group at alioth.debian.org.  Any
+maintainer/developer, either a DD or not, interested in Octave related
+packages is encouraged to join the pkg-octave project at Alioth.
 
+Issues are discussed in the pkg-octave-devel mailing list.  For more
+information about subscription and for looking at the archives, please
+visit http://lists.alioth.debian.org/mailman/listinfo/pkg-octave-devel
 
+Besides the common development of the Octave-related packages, the Debian
+Octave Group will eventually improve the common build infrastructure, which
+will result in a better integration of the packages in the Debian
+distribution.
+
+
 2. Building and uploading packages
 ----------------------------------
 
-Set maintainer to Debian Octave Group
-<pkg-octave-devel@lists.alioth.debian.org>
+The first thing to do when contributing a new package is to set the
+maintainer to Debian Octave Group <pkg-octave-devel@lists.alioth.debian.org>
+in debian/control.
 
-In debian/changelog, use:
+The debian/changelog entries should look like this:
 
 octave-cool (1.2.3-4) unstable; urgency=low
 
@@ -29,54 +39,73 @@
  
   * Cool tweaks 
 
- -- Debian Octave Group <pkg->  Mon,  15 Oct 2012 08:30:00 -0400
+ -- Debian Octave Group <pkg-octave-devel@lists.alioth.debian.org>  Mon,  15 Oct 2012 08:30:00 -0400
 
-At the end
 
+At the end of debian/changelog put the following lines:
+
 Local Variables:
 debian-changelog-full-name: "Debian Octave Group"
 debian-changelog-mailing-address: "pkg-octave-devel@lists.alioth.debian.org"
 End:
 
+This is a great help when using (X)Emacs with the debian-changelog-mode and
+hitting [(control) c] [(control) c].
 
+
 3. SVN repository
 -----------------
 
-Use Subversion : Tigurs.org, Svn-book file::///usr/share... package
-subversion 
+The packages are under Subversion control at svn.debian.org.  For more
+information on Subversion, please look at the web site
+http://subversion.tigris.org.  The Subversion book is also a valuable
+resource.  Install the subversion package and point your browser at 
+file::///usr/share/doc/subversion/book/.
 
-Automatic notifications
+Automatic SVN activity is sent to the pkg-octave-commit mailing list.  For
+more information, please visit
+http://lists.alioth.debian.org/mailman/listinfo/pkg-octave-commit 
 
-Repository organization
+The repository is organized as follows
 
-trunk/
-  packages/
-    octave2.1/
-      debian/
-    octave-forge/
-      debian/
-    [...]
-tags/
-  packages/
-    octave2.1/
-      debian/
-    octave-forge/
-      debian/
-    [...]    
-      
-Tagging convention ...
+    snv://svn.debian.org/svn/pkg-octave/
+      trunk/
+        packages/
+          octave2.1/
+            debian/
+          octave-forge/
+            debian/
+          [...]
+      tags/
+        packages/
+          octave2.1/
+            2.1.64-3/
+            2.1.64-4/      
+            [...]
+          octave-forge/
+            2004.11.16-3/
+            2004.11.16-4/
+            [...]
+          [...]
 
-Cookbook:
 
-# Import the repository
+Notice that only the debian files are put under Subversion control.  No
+upstream files, please.
 
+As regards tag conventions, use the following path:
+
+    svn://svn.debian.org/svn/pkg-octave/tags/packages/<package>/<version>
+
+Here is the cookbook to put a new package under Subversion control:
+
+# Import the pkg-octave repository
+
 svn co svn+ssh://svn.debian.org/svn/pkg-octave
 
-# Create the new directory in trunk 
+# Create the directory for the new package in trunk and tags
 
-cd pkg-octave/trunk/packages
-mkdir octave-cool
-cd ../../..
+mkdir pkg-octave/trunk/packages/octave-cool
+mkdir pkg-octave/tags/packages/octave-cool
 
 # Get the latest released version of the package
 
@@ -84,29 +113,29 @@
 
 # Copy the debian directory to trunk
 
-cp -a octave-cool-1.2.3/debian pkg-octave/trunk/octave-cool
+cp -a octave-cool-1.2.3/debian pkg-octave/trunk/packages/octave-cool
 
-# Add it to the repository
-cd pkg-octave/trunk/
-svn add octave-cool
+# Add the Debian-related files to the repository
+
+cd pkg-octave
+svn add trunk/packages/octave-cool
+svn add tags/packages/octave-cool
 svn commit --message 'Initial import of package octave-cool'
 
-# Tag its current version:
+# Tag its current version
 
-svn copy
-svn commit --message 'Debian release 1.2.3-4'
+svn copy trunk/packages/octave-cool tags/packages/octave-cool/1.2.3-4
+svn commit tags/packages/octave-cool --message 'Debian release 1.2.3-4'
 
-Now you can go back to the package sources and do:
+# Now you can go back to the package sources and do:
 
-cd ../../../octave-cool-1.2.3-4
+cd ../octave-cool-1.2.3-4
 rm -rf debian
-svn co svn+ssh://svn.debian.org/pkg-octave...debian
+svn co svn+ssh://svn.debian.org/svn/pkg-octave/trunk/packages/octave-cool/debian
 
-
-
-When committing changes that do not yet result in a release, keep
+When committing changes that do not result in a Debian release, keep
 debian/changelog in a clearly broken state, such that the other developers
-know that the version is not yet released.  Something like this:
+will know that the version is not yet released.  Something like this:
 
 octave-cool (1.2.3-4) unstable; urgency=low
 


Property changes on: trunk/README
___________________________________________________________________
Name: svn:keywords
   + Id