Hi all, Thanks for the numerous reports, workaround, efforts to get this thing clear.
After reading (sometimes skimming, sorry) all of them, I am coming to the conclusion that there are currently at least two issues: proper/updated dependencies and deb packages. PROPER/UPDATED DEPENDENCIES This is a moving target. Hugin is in development and every now and then new dependencies are added. It would be nice if developers adding those dependencies could give builders a heads-up so that builders won't have to guess / fix things on their own. The 'buntus evolve too. Packages are upgraded, renamed, retired, etc. There will always be a likelihood of breakage in the Wiki instructions between 'buntus releases. This is not an Ubuntu-only problem. The solution is to work patiently, methodically, recursively through the messages printed by CMake. I've started a new wiki page [0] for developers, builders, maintainers. It is still work in progress. Developers: please read it so that at least we don't "break" things. DEB PACKAGES 1. CMake deb package generation is broken [1]. This is not new, but has not prevented the Wiki instructions from working until now. 2. dpkg was tolerant of this in the past. Now it throws an error if a folder does not exist / is not created properly. A well crafted deb package creates folders properly. 3. The short-term solution is to list the missing folders and create them, either manually or within the deb package. Dale has worked on listing the folders, while Kornel provided an initial shell script to be added to the CMake build. This affects Hugin, but also Libpano and Enblend packages. 4. Packages built to install into the canonical location (/usr) work -- simply because the folder exist previously, not because they are better packages. But installing these experimental builds in the canonical location interferes with the official distribution packages who install in the same place and with the same name. 5. The long-term solution is to distribute proper deb packages, and the way to build them is to use a PPA [2], uploading a source package [3] and letting the Ubuntu/Canonical infrastructure do the building, making sure that the package complies with the proper specifications [4]. 6. There is already a Hugin PPA [5] with packages contributed by Philipp Seidel about six months ago. It can definitely use an update and help is welcome. Yuv [0] http://wiki.panotools.org/Fixing_The_Hugin_Build [1] http://groups.google.com/group/hugin-ptx/msg/3f29b207c562fd63 [2] https://help.launchpad.net/Packaging/PPA [3] https://help.launchpad.net/Packaging/PPA/Uploading [4] https://wiki.ubuntu.com/PackagingGuide/Complete [5] https://launchpad.net/~hugin
signature.asc
Description: This is a digitally signed message part.
