1.1 --- a/README.txt Sat Jun 25 02:43:01 2011 +0200
1.2 +++ b/README.txt Sat Jun 25 17:19:27 2011 +0200
1.3 @@ -8,12 +8,19 @@
1.4
1.5 The idea is then to combine the snapshot with this packaging infrastructure.
1.6
1.7 -Unpack and move into the sources directory:
1.8 +Unpack the archive:
1.9
1.10 cd ..
1.11 tar zxf shedskin-mainline-7f7388c.tar.gz
1.12 -mv shedskin-mainline shedskin-mainline-7f7388c
1.13 -cd shedskin-mainline-7f7388c
1.14 +mv shedskin-mainline shedskin_0.8
1.15 +
1.16 +Make a copy of the archive for Debian non-native packaging purposes:
1.17 +
1.18 +tar zcf shedskin_0.8.orig.tar.gz shedskin_0.8
1.19 +
1.20 +Move into the sources directory:
1.21 +
1.22 +cd shedskin_0.8
1.23
1.24 Now, copy the debian directory from this directory into the export directory:
1.25
1.26 @@ -36,6 +43,14 @@
1.27
1.28 pdebuild --auto-debsign --debsign-k 9F308B3C
1.29
1.30 +Add extra options for the first packaging of a new release:
1.31 +
1.32 +pdebuild --auto-debsign --debsign-k 9F308B3C --debbuildopts -sa
1.33 +
1.34 +This makes sure that the original source archive is produced and referenced in
1.35 +the changes file (used by dput when uploading a package to a Debian package
1.36 +repository/archive).
1.37 +
1.38 Some files will appear in /var/cache/pbuilder/result/ (such as the binary
1.39 package files), whereas others will appear in the parent directory.
1.40
1.41 @@ -45,7 +60,10 @@
1.42 When packaging a new release, update the release history below along with the
1.43 debian/changelog file:
1.44
1.45 -debchange -v 0.8 -D unstable
1.46 +debchange -v 0.8-1 -D unstable
1.47 +
1.48 +The "-n" part of the version number causes a non-native Debian package to be
1.49 +produced.
1.50
1.51 Shed Skin Release History
1.52 =========================