[ELPA-diffs] /srv/bzr/emacs/elpa r318: Refine the deployment script to avoid deploying unstable code.

[Stefan Monnier]

------------------------------------------------------------
revno: 318
committer: Stefan Monnier <address@hidden>
branch nick: elpa
timestamp: Wed 2012-12-05 10:31:58 -0500
message:
  Refine the deployment script to avoid deploying unstable code.
added:
  packages/README
modified:
  admin/update-archive.sh

=== modified file 'admin/update-archive.sh'
--- a/admin/update-archive.sh   2012-11-29 15:58:17 +0000
+++ b/admin/update-archive.sh   2012-12-05 15:31:58 +0000
@@ -84,10 +84,12 @@
      # FIXME: it'd be better to only rebuild the packages that have been
      # modified, rather than rely on md5 to try and abort the refresh
      # when we don't want it!
-     if [ -r "$dst" ] && [ "$(md5sum <"$f")" = "$(md5sum <"$dst")" ]; then
-         rm "$f"
-     else
-         mv "$f" "$dst"
+     # Actually, let's never overwrite an existing version.  So changes can
+     # be installed without causing a new package to be build until the
+     # version field is changed.
+     if [ -r "$dst" ] # && [ "$(md5sum <"$f")" = "$(md5sum <"$dst")" ]
+     then rm "$f"
+     else mv "$f" "$dst"
      fi
  done
  mv build/archive/"$latest" staging/

=== added file 'packages/README'
--- a/packages/README   1970-01-01 00:00:00 +0000
+++ b/packages/README   2012-12-05 15:31:58 +0000
@@ -0,0 +1,11 @@
+This directory contains most of the source code of the GNU ELPA packages.
+
+Each directory in here corresponds to a package, which can be
+either a single-file package or a multifile package.
+
+A nightly cron job refreshes the GNU ELPA archive from this repository.
+
+This cron job only creates a new package when the "version" of a package
+is modified.  This means that you can safely work on the next version here
+without worrying about the unstable code making it to GNU ELPA, and simply
+update the "version" when you want to release the new code.