I was waiting for a fix for the Vala issue (which I just backported from Git yesterday), before finishing my Postler packaging -- sorry for the duplicate request!
Thomas, let me know if you'd like a comaintainer for this. I have some differences in my specs:
- CFLAGS needs to be manually exported; when packaging I searched for any guidelines for packaging with waf (we still really need to write one!) Funnily all the people involved in that thread on the mailing list are here -- me, you (waf maintainer) and Christoph who started the thread.
- waf build probably needs the -v option (verbose) -- that's how I discovered
the wrong compiler flags were being used, and %{?_smp_mflags}
- link against libdb-devel (BerkeleyDB 5) rather than db4
- use system waf rather than the bundled version
Also, I started using the virtual pkgconfig(...) rather than package names, as they match up with upstream's dependency checking better.
I was waiting for a fix for the Vala issue (which I just backported from Git yesterday), before finishing my Postler packaging -- sorry for the duplicate request!
Thomas, let me know if you'd like a comaintainer for this. I have some differences in my specs:
- CFLAGS needs to be manually exported; when packaging I searched for any guidelines for packaging with waf (we still really need to write one!) Funnily all the people involved in that thread on the mailing list are here -- me, you (waf maintainer) and Christoph who started the thread.
- waf build probably needs the -v option (verbose) -- that's how I discovered
the wrong compiler flags were being used, and %{?_smp_mflags}
- link against libdb-devel (BerkeleyDB 5) rather than db4
- use system waf rather than the bundled version
Also, I started using the virtual pkgconfig(...) rather than package names, as they match up with upstream's dependency checking better.