summaryrefslogtreecommitdiff
path: root/debian/README.Debian
diff options
context:
space:
mode:
authorReinhard Tartler <siretart@tauware.de>2017-06-17 17:57:17 -0400
committerReinhard Tartler <siretart@tauware.de>2017-06-17 17:57:37 -0400
commitacedb46a3e41f97fc9fedb731d7a286be7104dde (patch)
treeeca680b94ccfcd9992754ec6afb49e1c70cc2c19 /debian/README.Debian
parentc8c7c2b1d777126fcb36929463d66a8f0a381975 (diff)
Clarify how the upstream tarball is produced
The "upstream" tarball is produced using git-archive from the upstream git branch at github:
Diffstat (limited to 'debian/README.Debian')
-rw-r--r--debian/README.Debian16
1 files changed, 4 insertions, 12 deletions
diff --git a/debian/README.Debian b/debian/README.Debian
index 269c598f..749da0cb 100644
--- a/debian/README.Debian
+++ b/debian/README.Debian
@@ -109,17 +109,9 @@ http://www.boxbackup.org
"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.
+The "upstream" tarball is produced using git-archive from the upstream
+git branch at github:
-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.
+https://github.com/boxbackup/boxbackup
-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, 14 Jun 2017 21:02:45 -0400
+ -- Reinhard Tartler <siretart@tauware.de>, Sat, 17 Jun 2017 17:57:00 -0400