#10 dpkg

[schoenborno]

Shane (smfinzer) emailed me this:

Hello, I had to debian packag-ize pubsub for my company and wanted to send you the update.
I would advise you to update your email on the sf page as it is no longer valid.
...
By the way I changed certain strings that you should customize, e.g.

About the changelog: The version here should be replaced with whatver your internal version (3.1.1b1??), '-263-1' is what our auto version script concatenated to your interval version number. COMPANY, mail@mail.com & the date should also be customized.. the same goes for the control file.

Note: The rules file contains commented out code related to your documentation, you might want to uncomment it and see if it works, I had problems with sphinx-build myself.

The README and CHANGELOG are required dpkg files, I Ieft them blank, you may wish to write something meaningful in them.

So all you need to do is extract the files from the tar into your root pubsub dir and then build via 'dpkg-buildpackage -rfakeroot'. It should list any missing dependencies req. for building the package...

I think dpkg-dev is one of them install like this: 'sudo apt-get install dpkg-dev'. The built package will end up one dir above, and you can test the installation like this (assuming you are in the dir where you built the package) '../sudo dpkg -i insertpackagenamehere.deb'.

One last thing, whenever you have a new version all you do is add an entry to the top of debian/changelog, that is where dpkg gets the package version from. Here is an example:

http://packages.debian.org/changelogs/pool/main/d/dpkg/dpkg_1.16.0.3/changelog

Come to think of it you can remove the '(Package signing key)' text.
Regarding the email, looks like I did not select the last character when copy pasting it :-[

[schoenborno]

I have a Linux VM but no easy access to it, will dig it up ASAP