[ please don't top-post on mailing-lists -- rearranged for readability] On 01/17/2012 01:24 PM, Louigi Verona wrote: You're welcome. that may be a suitable short-term solution, but why not do it properly and package it upstream at debian? http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=594784 robin

On 01/17/2012 03:25 PM, Louigi Verona wrote: by doing it :) It's the same process as creating PPA packages. Though, for Debian one needs to be a bit more diligent (the package must have proper license information, a man page and .desktop file,.. IOW be 'lintian clean' & DEP-3 compliant) and become approved (find a 'sponsor' for your uploads). details are at http://wiki.debian.org/DebianMultimedia/DevelopPackaging After you're done, you can also push it into a PPA until the package trickled down the debian-queue to your distribution/release. I'm on it; call git-buildpackage on https://github.com/x42/paulstretch_cpp/tree/master/ robin

On 01/19/2012 05:38 AM, Louigi Verona wrote: Looks like you forgot to cd into the source-dir. more below. Maybe. If music is what you want to do, don't bother to become a DD. OTOH (personal- and otherwise-) packages can save lots of time (e.g. cleaning up /usr/local/ when a new project eventually hits your distribution; or deploying custom software on more than one machine, and sharing it easily) Let's start at the end: building the package (from git) cd /tmp/ git clone git://github.com/x42/paulstretch_cpp.git cd paulstretch_cpp/ git checkout -b upstream origin/upstream git checkout master git-buildpackage -rfakeroot -b -us # ^ may complain about missing build-deps, apt-get install them # and re-run git-buildpackage ls ../*deb sudo dpkg -i ../*deb The options "-rfakeroot -b -us" options are passed on to `debuild`, or `dpkg-buildpackage`: -b: build binary only; -us: don't GPG sign it. To create a source (and binary) packages directly from git, but built them in a dedicated folder outside the git-repo: TMPDIR=/tmp/mybuild mkdir ${TMPDIR} git-buildpackage \ --git-upstream-branch=upstream --git-debian-branch=master \ --git-upstream-tree=branch \ --git-no-pristine-tar --git-force-create \ --git-export-dir=${TMPDIR} -rfakeroot # -us -uc #validate the package: lintian -i --pedantic `ls -t ${TMPDIR}/*changes | head -n1` #upload it somewhere -- ; man dput.cf; edit ~/.dput.cf dput somehost `ls -t ${TMPDIR}/*changes | head -n1` It's less complex than you may think. As usual, the tricky part is the politics - not technical issues. That's also the reason why PPAs have become popular: don't bother about policy :) For a minimal .deb package you /only/ need 4 files: debian/changelog -- version-num, target-distribution, history debian/control -- package-name, dependencies, description debian/rules -- build instructions (makefile) debian/compat -- just a number. Just check out some existing packages, copy, paste, edit. There's also lots of documentation and tutorials around. It may take you only an hour or two to learn the basics. `dh_make` is an easy way initially populate debian/* with example files. Beyond the basics, it can indeed become an odyssey, esp. if you want to create binaries for all architectures, multiple distributions, etc. (pbuilder, cowbuilder) yourself. but one usually outsources that. Also, shared-libs require a bit of special attention.. In my experience, the most time-consuming part in debian packaging is writing man-pages!! Debian Policy section 12.1: "Each binary [..] should have a manual page included in the same package". YMMV. They are dead-useful. robin