1 Shed Skin Packaging for Debian
2 ==============================
3
4 Firstly, download the latest upstream source release. Although it might be
5 desirable to get the latest code from the repository, Debian will eventually
6 be using the actual source releases specified in the watch file.
7
8 However, one can try and persuade Gitorious to yield a file by visiting the
9 following address:
10
11 http://gitorious.org/shedskin/mainline/archive-tarball/31b8214
12
13 The digest string can be replaced with a tag:
14
15 http://gitorious.org/shedskin/mainline/archive-tarball/0.9
16
17 The idea is then to combine the snapshot with this packaging infrastructure.
18
19 Unpack the archive:
20
21 cd ..
22 tar zxf shedskin-mainline-31b8214.tar.gz
23 mv shedskin-mainline shedskin_0.9
24
25 Make a copy of the archive for Debian non-native packaging purposes:
26
27 tar zcf shedskin_0.9.orig.tar.gz shedskin_0.9
28
29 Move into the sources directory:
30
31 cd shedskin_0.9
32
33 Now, copy the debian directory from this directory into the export directory:
34
35 cp -R ../shedskin-packaging/debian/ .
36
37 There are patches in debian/patches which should be applied when pbuilder is
38 run. These should not need to be applied manually.
39
40 Using pbuilder, try and build the package (this example is using my signing
41 key):
42
43 pdebuild --auto-debsign --debsign-k 9F308B3C
44
45 Add extra options for the first packaging of a new release:
46
47 pdebuild --auto-debsign --debsign-k 9F308B3C --debbuildopts -sa
48
49 This makes sure that the original source archive is produced and referenced in
50 the changes file (used by dput when uploading a package to a Debian package
51 repository/archive).
52
53 For a different distribution:
54
55 pdebuild --auto-debsign --debsign-k 9F308B3C --debbuildopts -sa \
56 -- --distribution squeeze
57
58 Some files will appear in /var/cache/pbuilder/result/ (such as the binary
59 package files), whereas others will appear in the parent directory.
60
61 Maintenance Notes
62 -----------------
63
64 When packaging a new release, update the release history below along with the
65 debian/changelog file:
66
67 debchange -v 0.9-1 -D unstable
68
69 The "-n" part of the version number causes a non-native Debian package to be
70 produced.
71
72 Shed Skin Release History
73 =========================
74
75 Release Git Changeset
76 ------- -------------
77 0.9 31b8214b451d87fae5ec7194a7b4430daa3f49ce
78 0.8-1 d7cf784f5e12952a5630f6b78b3155995c825a38
79 0.8 7f7388c3dfab40dc1776cfd6334dd41bdaa62beb
80 0.7.1 d35a07c99c29618e0dad6d31a3cf01599c0d758a
81 0.7 8fc85b49137a79ca9acc5e63fa9fdfbb50751907
82 0.6 1e6708d49e9092a7949ed74b7e339c5245bb6661
83
84 Release Subversion Revision
85 ------- -------------------
86 0.5 1507
87 0.4 1363
88 0.3-2 1165
89 0.3-1 1165