1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
|
Node-svgdotjs-svg.js packaging workflow
---------------------------------------
Node-svgdotjs-svg.js uses git-buildpackage for the packaging maintenance.
Its source is split off into the main application and some additional
add-ons like "panzoom" and "draggable" which enhance the basic features.
We use component tarballs to collect all the sources. git-buildpackage is able
to handle those files for importing into the git tree as also for extracting
the correct component tarballs later if needed. For the recreation of the
orig*.tar.xz pristine-tar is doing the correct action.
The source tarball and the additional component tarballs are currently created
manually from cloned upstream git repositories. Normally the following calls
are used to create the tarballs.
$ cd /path/to/node-svgdotjs-tree
$ git archive --format=tar.gz --output ../node-svgdotjs-svg.js_3.2.5.orig.tar.gz 3.2.5
$ cd /path/to/node-svgdotjs_panzoom-tree
$ git archive --format=tar.gz --output ../node-svgdotjs-svg.js_3.2.5.orig-panzoom.tar.gz 3.2.5
Importing new source tarballs is done by git-buildpackage with adding the
suffix 'dfsg' to the version to import.
$ gbp import-orig --verbose --pristine-tar /path/to/node-svgdotjs-svg.js_3.2.5.orig.tar.gz
...
What is the upstream version? [3.2.5] 3.2.5+dfsg
...
The multi tarballs will be extracted to the following folders while importing
the new version:
*.orig-panzoom.tar.gz -> panzoom/
*.orig-draggable.tar.gz -> draggable/
-- Georges Khaznadar <georgesk@debian.org>, Sun Sep 28 14:48:39 CEST 2025
|
