> On Sep 12, 2018, at 10:19 AM, Cristian Ionescu-Idbohrn > <[email protected]> wrote: > > On Tue, 11 Sep 2018, Dirk Hohndel wrote: >> >> The packaging of private Qt headers changes - I believe they simply >> got dropped (which is not entirely unreasonable given that they are, >> you know, private). As a result in a completely clean build we are >> now downloading them directly and a clean build on Debian and Ubuntu >> /should/ work - I did one on 18.04 a few days ago and that went >> smoothly. > > Alright. "a completely clean build" seems to work, but I wouldn't > call that sanity, should I?
I don't think I would use sanity and distro packaging in the same context. That said, this one is partly our fault... we use a module that uses private headers from Qt. Debian/Ubuntu decided to stop packaging those. We don't notice and don't trigger the actions that do have the code for (downloading the matching private header and re-compiling against them). It would be nice if someone figure out a way to check this dependency and to automatically do the right thing. I'll admit that given how few people compile from source and how even fewer do so on Debian/Ubuntu systems and how rarely Qt versions change... yeah, this isn't really high on my TODO list, TBH /D _______________________________________________ subsurface mailing list [email protected] http://lists.subsurface-divelog.org/cgi-bin/mailman/listinfo/subsurface
