[DRE-commits] [ruby-rspec] 08/14: add README.source

Cédric Boutillier boutil at moszumanska.debian.org
Wed Apr 1 23:29:52 UTC 2015


This is an automated email from the git hooks/post-receive script.

boutil pushed a commit to branch master
in repository ruby-rspec.

commit 0d4387d1c9c455fd57153e78f5e970cc8c7d90ac
Author: Cédric Boutillier <boutil at debian.org>
Date:   Thu Apr 2 01:04:26 2015 +0200

    add README.source
---
 debian/README.source | 41 +++++++++++++++++++++++++++++++++++++++++
 1 file changed, 41 insertions(+)

diff --git a/debian/README.source b/debian/README.source
new file mode 100644
index 0000000..e8921b2
--- /dev/null
+++ b/debian/README.source
@@ -0,0 +1,41 @@
+This package is maintained in a Git repository on Alioth.
+
+It uses the Debian 3.0 (quilt) source format, with multiple upstream tarballs.
+As such, it cannot follow the typical workflow with git-buildpackage as
+git-buildpackage doesn't support (yet?) multiple tarballs.
+
+The upstream version has the following form: x.y.0c1e2m3s4-z
+x.y corresponds to the major/minor version of rspec.
+first number after x.y (0 in the example):
+  the number of the revision for rspec gem 
+number after c: revision for rspec-core
+number after e: revision for rspec-expectations
+number after m: revision for rspec-mocks
+number after s: revision for rspec-support
+
+
+The workflow for the moment is the following:
+
+update to a new upstream version
+--------------------------------
+
+use the following targets from debian/rules:
+
+- debian/rules get-orig-sources: 
+    download and create the multiple upstream tarballs
+- debian/rules unpack-sources:
+    unpack the sources, to be committed in the upstream branch
+    (awkward, because debian/rules is not present in the upstream branch...)
+- debian/rules gen-gemspecs:
+    interpret upstream 'source' gemspec to real ones, with shell commands
+    (calls to git), and store them in the debian/ directory
+    to be committed to the master branch
+    update then debian/patches/gemspecs.patch with the diff between upstream
+    source gemspecs and the generated ones.
+
+dpkg-source automatically creates an empty upstream main tarball for the source
+package, and will use the several components tarball.
+
+The tarballs are stored in the pristine-tar branch.
+
+ -- Cédric Boutillier <boutil at debian.org> 2015-04-01

-- 
Alioth's /usr/local/bin/git-commit-notice on /srv/git.debian.org/git/pkg-ruby-extras/ruby-rspec.git



More information about the Pkg-ruby-extras-commits mailing list