From a developer perspective it is a very simple concept: source packages are
uploaded to a clean automated build system. At https://launchpad.net/~hugin/+archive/nightly the uploads are automatic as
well (nightlies). In case of success there is a new nightly to install/test.
In case of failure there is a failure log that can help debugging. As a
member of Hugin PPA I receive emails with links to the failed build logs.
On March 7, 2011 12:13:20 PM tmodes wrote:
> I have no experience with PPA.
The PPA is documented at http:// wiki.panotools. org/Hugin_ PPA in more detail
than a developer really need to know.
From a developer perspective it is a very simple concept: source packages are /launchpad. net/~hugin/ +archive/ nightly the uploads are automatic as
uploaded to a clean automated build system. At
https:/
well (nightlies). In case of success there is a new nightly to install/test.
In case of failure there is a failure log that can help debugging. As a
member of Hugin PPA I receive emails with links to the failed build logs.
You can see all build logs (more than 400 of them) at /launchpad. net/~hugin/ +archive/ nightly/ +builds? build_text= &build_ state=all
https:/
> I added a more general FindTclap.cmake.
> Please test.
The latest I received :(
http:// launchpadlibrar ian.net/ 66165728/ buildlog_ ubuntu- maverick- 2010.5. 0%2B2011. 0.0%2Bhg5099- 0ubuntu1~ maverick_ FAILEDTOBUILD. txt.gz
i386.hugin_
I'm setting up a build environment on my Natty netbook now and will try the
attached FindTclap.cmake later.
Yuv
status new