summaryrefslogtreecommitdiff
path: root/debian/README.Debian
diff options
context:
space:
mode:
authorReinhard Tartler <siretart@tauware.de>2009-04-01 09:53:27 +0200
committerReinhard Tartler <siretart@tauware.de>2009-04-01 09:53:27 +0200
commitdd5db5cf9a42fe6708d2287c28f1afca33bf8f95 (patch)
treec136173882e2ed8edaf8de6d18766727aec4d955 /debian/README.Debian
parent2bad12911670b4467fe5ab799193a68ef18838af (diff)
add some notes about the upstream tarball situation
Diffstat (limited to 'debian/README.Debian')
-rw-r--r--debian/README.Debian19
1 files changed, 18 insertions, 1 deletions
diff --git a/debian/README.Debian b/debian/README.Debian
index 5ad55934..88c1d553 100644
--- a/debian/README.Debian
+++ b/debian/README.Debian
@@ -105,4 +105,21 @@ bbstored-certs ca sign clientaccount-csr.pem
You will find a more detailled documentation on the boxbackup Web site:
http://www.fluffy.co.uk/boxbackup/
- -- Reinhard Tartler <siretart@tauware.de>, Wed, 25 Apr 2007 18:04:01 +0200
+
+"Upstream" tarball
+------------------
+
+Althogh upstream indeed publishes tarballs, the debian package is no
+longer based on these tarballs. The reason for this is that the
+procedure for creating these tarballs makes package maintenance and
+interaction with upstream unnecessary hard.
+
+Moreover, there seem to be different types of tarballs. Official ones
+used for a release and "unofficial" ones that are created for snapshot
+releases, causing further confusion.
+
+Since upstream releases rather seldomly, but we want to distribute
+pre-releases and integrate patches from the upstream svn, the package
+ships a script in the source that is used to create the orig.tar.gz.
+
+ -- Reinhard Tartler <siretart@tauware.de>, Wed, 1 Apr 2009 09:53:08 +0200