--- a/demopublishpackages.cfg	Wed Apr 15 13:50:31 2009 +0000
+++ b/demopublishpackages.cfg	Thu Apr 16 09:32:35 2009 +0000
@@ -9,6 +9,11 @@
 distribution: lenny
 section: experimental
 
+# Number of newest successfully builts revisions to publish for each
+# track.  Ignored when publishpackages is called with an explicit
+# revision.
+num_newest: 3
+
 # Username and host on which the treepackager runs.  publishpackages.py
 # has to be able to connect to that host as the builduser via ssh
 # without knowning the password.  This is best achieved with the
@@ -23,16 +28,25 @@
 
 # Username and host on which to publish the packages.
 # publishpackages.py uses ssh to execute commands on the publish_host to
-# create directories and scp to copy the files from the local cache to
-# the publish_host.
+# create directories and rsync to copy the files from the local cache to
+# the publish_host.  If publish_host is empty, the publishpackages.py
+# assumes that no ssh or other remote login is needed to access the
+# publish host with the right permissions.
 publish_user: builder
 publish_host: localhost
 
 # the directory on the publish_host where the apt directories reside.
 publish_dir: /home/ftp/apt/dists/
 
-# Command to execute on the build host to update the apt archive
-publish_apt_archive_update: /home/ftp/apt/update
+# If true publishpackages.py will remove the packages in publish_dir
+# that were not put there by the current run.  Setting it to True is
+# probably only useful when using publishpackages.py to automatically
+# publish the newest built packages using a cron-job, for instance.
+publish_remove_old_packages: False
+
+# Command to run after the packages have been copied to the publish
+# host.  This command is run on the host running publishpackages.py.
+after_upload_hook: ssh %(publish_user)s@%(publish_host)s /home/ftp/apt/update
 
 # local cache directory.  publishpackages.py may delete it and its
 # contents, so if you intend to run publishpackages.py on the same