Thanks for the instructions, Andreas. They do work. A few questions below, but first a public announcement: Philipp has updated the Ubuntu PPA.
On October 17, 2010 12:04:05 pm Andreas Metzler wrote: > Yuval Levy <goo...@levy.ch> wrote: > [...] > > > The Hugin PPA [3] can use an update. The packages contributed by > > Philipp Seidel about six months ago are 2010.0.0 and for Karmic and > > Lucid only. Philipp has updated the PPA, so getting the best Hugin ever for Ubuntu is as easy as starting a command line and typing three commands. STABLE: sudo add-apt-repository ppa:hugin/hugin-builds sudo apt-get update sudo apt-get install hugin enblend autopano-sift-c panini "NIGHTLY" (very near to the bleeding edge) sudo add-apt-repository ppa:hugin/hugin-builds sudo add-apt-repository ppa:hugin/nightly sudo apt-get update sudo apt-get install hugin enblend autopano-sift-c panini The binaries are still mostly for lucid and for maverick. We'll have to check if there is a need to support older versions (any 'buntu user out there using anything older than 10.4?) and how to do it. > If you have got experimental[1] in sources.list this should work: thanks for the instructions, Andreas. They do work. A few questions. > edit Maintainer and/or Uploaders in debian/control [2] and I guess Build-Depends: when an added dependency is introduced? the list in the control file is much shorter than what I need to enter when building with CMake [0]. Should control be updated to reflect the CMake build dependencies? Or is there a reason to keep the list short (and maybe incomplete)? > debemail=yourm...@address dch --newversion 2.9.17+dfsg-2~huginppa1 rebuilt man dch says it is a good idea to set DEBEMAIL and DEBFULLNAME, which I did in ~/.bashrc. But on Kubuntu (10.4) it still uses u...@host even though echo $DEBEMAIL returns the expected result. Is this Ubuntu-only, or also in Debian? > debsign -k<ppa-keyid> resulting_changes the longest part for this was to set up / validate the key in Launchpad. Everything else was very easy. > Upload. https://help.launchpad.net/Packaging/PPA/Uploading > > Wait a day or two to give the buildd a chance to build binaries of > libpano13-2. a day or two? actually it was less than an hour. I would appreciate feedback on the first Ubuntu binary package I have ever published [1]. Next come a few questions: * how can I use my machine (Lucid) to serve PPA builds for other 'buntu series? * how do I know for which target architecture the binaries were built? is it default i386? AMD64? both? > [as root] apt get build-dep hugin=2010.2.0+dfsg~rc2-1 I'm getting at Hugin now, which is obviously more complicated than Libpano. Do I understand correctly that the ./debian folder is all what is added to a plain unpacked tarball? i.e. if I would like to do a bleeding edge build rather than a 2010.2.0 build, could I simply copy the ./debian folder into a clean repo checkout, update the control file with newly added dependencies and reasonably expect that it would work in most cases? thanks again, Andreas Yuv [0] http://wiki.panotools.org/Hugin_Compiling_Ubuntu#Dependencies [1] https://launchpad.net/~yuv/+archive/yuv-stuff
signature.asc
Description: This is a digitally signed message part.
