Comment 3 for bug 1050586

Well, actually I *did* read the README first, and I think that is the most confusing part.
(Maybe i should mention that I used the released version, 0.5.5, not git, as i assumed it to be more reliable - the git README seems improved a little)

It talks about a DEPENDENCIES file which does not exist, continues with the source directory, which does not exist and about configure, which does also not exist, not even in "src" which would be my best guess for the "source" directory.

I figured the README is outdated and i have to adapt its information, for example i assumed that 'prepare' is the new 'configure', although i wondered who in the world would do that to improve a package...

I also saw the "Build dependencies" and "Dependencies" sections but it didn't explicitly say development files. I don't know in which way sqlite is used and also which components need it. "Qt4, GTK2 and NoX" is unspecific about what you need for which parts.

Also, that I had to patch the .pm files that ligcc uses did not improve my confidence in the package - it seemed to me the package is totally broken and nobody can really use it. And as there is no new release after several months, i was afraid nobody would care... In total, i worked around 2 problems and gave up on the third, probably the one that qualifies as bug the least. I apologize :)

Again, i don't think a configure script is confusing if it works as expected.
As i said, it quit on me *WITHOUT echoing one word!*
The lines

CMAKE=$(which cmake)
if [[ $? -gt 0 ]]; then
  echo "CMake was not found! Please install cmake."
  exit 8
fi

don't do what they are supposed to do - the if statement is never reached (!!!) if cmake is not installed - that is a flaw in the script, although i dont understand why it terminates abnormally on "which cmake". - Maybe actually a flaw in the 'which' script of Ubuntu 12.04.

By removing the script, you remove this flaw, but the main reason for my bug report was that cmake gave me an error that i was not able to parse properly :) Of course, this message is the same if cmake is used directly.

A line like "Checking for sqlite development files... FAIL" would probably have helped me... :)