rev 6664 - kde-extras/digikam-doc/trunk/debian

[Mark Purcell]

Author: msp
Date: 2007-07-04 06:46:27 +0000 (Wed, 04 Jul 2007)
New Revision: 6664

Modified:
   kde-extras/digikam-doc/trunk/debian/README.Debian
Log:
Sync README.Debian

Modified: kde-extras/digikam-doc/trunk/debian/README.Debian
===================================================================
--- kde-extras/digikam-doc/trunk/debian/README.Debian	2007-07-04 06:45:47 UTC (rev 6663)
+++ kde-extras/digikam-doc/trunk/debian/README.Debian	2007-07-04 06:46:27 UTC (rev 6664)
@@ -32,16 +32,16 @@
 The repository layout is:
 
 - packagename/
-    - trunk/
-    - branches/
-    - tags/
-        - 0.7.2-1/
-        - 0.7.2-2/
-        - 0.7.2-2ubuntu1/
-        - 0.7.2-2ubuntu2/
-        - 0.7.2-2ubuntu3/
-        - 0.8.0/
-        ...
+Â  Â  - trunk/
+Â  Â  - branches/
+Â  Â  - tags/
+Â Â Â Â Â Â Â Â - 0.7.2-1/
+Â Â Â Â Â Â Â Â - 0.7.2-2/
+Â Â Â Â Â Â Â Â - 0.7.2-2ubuntu1/
+Â Â Â Â Â Â Â Â - 0.7.2-2ubuntu2/
+Â Â Â Â Â Â Â Â - 0.7.2-2ubuntu3/
+Â Â Â Â Â Â Â Â - 0.8.0/
+Â Â Â Â Â Â Â Â ...
 
 If only one version of the package is available at the time, development must 
 be made at trunk/ dir, copying the dir to tags/'pkg-version' each time a new 
@@ -105,3 +105,42 @@
 uploaded to the archive.  Note you will also need to manually copy the
 package.orig.tar.gz to your tarballs directory.  The -o option is important as
 this ensures that we 'Only keep modified files under SVN control'
+
+6. Versioning
+-------------
+
+As the autobuilder and fellow developers will need to differentiate between
+versions that are uploaded into debian already and those which will be at a
+later point, do use the UNRELEASED distribution until the time you actually do
+upload to incoming. Whoever is not a DD himself should let the sponsor do that
+final step if that sponsor has SVN commit rights to the kde-extras archive.
+
+The autobuilder packs can be found at http://kde-extras.buildserver.net/.
+The logs can be found at http://status.buildserver.net/.
+
+As the archive runs britney, it may well be that a built and installed package
+is not appearing to the archive until its reverse depends are (re)built too. In
+case of questions, feel free to mail kilian at debian.org.
+
+7. Automatic Backport hooks
+---------------------------
+
+The checkout script for putting together the sources can run a backports hook
+for certain dists (like Debian sarge) which need certain adjustments to the
+source like altered Build-Depends. This hook is a plain shell script (or
+makefile like debian/rules) which needs to be put in the debian/backports
+directory and made executable by means of the svn properties set. The codenames
+for the current dists are: sid, etch, sarge, edgy and dapper. For an example
+see asterisk-addons/trunk/debian/backports/sarge which may be more illustrating
+what to do.
+
+8. Autotools, libtool, am_maintainer, buildprep and configure updates
+---------------------------------------------------------------------
+
+Achim, Please add some text in here to document when it is necessary and
+how we update the build enviroment for a package.
+
+-(snip)-
+
+In case any of the above is unclear to you or seems outdated, please drop us a
+note to the maintainers list.