Yuval Levy <[email protected]> wrote: [....] > On October 17, 2010 12:04:05 pm Andreas Metzler wrote: [...] >> 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? Yes, but ... > 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)? The goal is too keep the list somehow minimal. As it is it works for 2010.2.0. I am pretty sure the lists in the Ubuntu wiki is inflated boost-build should not be necessary at all (the package description suggests this is a cmake or auto* replacement). The number of libboost-*-dev packages differs. Different versions of boost are split up differently. (e.g. on Debian/stable adding libboost-date-time-dev is necessary) libxi-dev and libxmu-dev are unecessarily pulled in, we patch this (42_stoplinklibXI_libXmu). I am not sure about liblapack-dev, I thought I read somewhere that not linking hugin against external lapack was preferable. >> 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? I works for me on debian. ;-) [...] > I would appreciate feedback on the first Ubuntu binary package I have ever > published [1]. Looks good. > Next come a few questions: > * how can I use my machine (Lucid) to serve PPA builds for other 'buntu > series? The ppa service builds for the distribution listed in debian/changelog, (lucid in your case). I do not know what the best way to get binaries for multiple releases, I guess you'll need multiple uploads. And chroots/test installations. > * how do I know for which target architecture the binaries were built? is it > default i386? AMD64? both? The ppa autobuilder builds for both i386 and amd64. [...] > Do I understand correctly that the ./debian folder is all what is added to a > plain unpacked tarball? Correct. (That holds for dpkg-source v3 packages.) > 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? [...] That is about it. Except for: * debian/changelog (That is where the version number comes from.) * debian/patches/*. You might need to refresh patches or drop patches included upstream by deleting them and dropping tem from debian/patches/series. cu andreas -- `What a good friend you are to him, Dr. Maturin. His other friends are so grateful to you.' `I sew his ears on from time to time, sure' -- You received this message because you are subscribed to the Google Groups "Hugin and other free panoramic software" group. A list of frequently asked questions is available at: http://wiki.panotools.org/Hugin_FAQ To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/hugin-ptx
