[Development] Linux release binaries too old

[Blasche Alexander]

--
Alex


> -----Original Message-----
> From: development-bounces+alexander.blasche=digia.com at qt-project.org
> [mailto:development-bounces+alexander.blasche=digia.com at qt-project.org]
> On Behalf Of Thiago Macieira


> That would mean these are the minimum versions the popular distros (release
> month in parentheses):
> 	Arch (rolling release)
> 	CentOS 7.0 (7/2014)
> 	Debian testing (no release!)
> 	Fedora 17 (5/2012)
> 	Mageia 3 (5/2013)
> 	Mint 13 (5/2012)
> 	OpenSUSE 12.2 (9/2012)
> 	Ubuntu 12.04 (4/2012)

Ok, I agree that we cannot leave stable Debian behind. 

However I'd like to clarify how and where we formalize which of the distros above we care about and/or what condition must be fulfilled when doing an upgrade. Not every case is as clear cut as the Debian one.  There is no formalization or reference page that I can find. Our docs only talk about 11.10, 12.04 and occasional 11.04 tests. 
 
> In other words, by upgrading our Ubuntu 11.10 build, we'll drop support for
> any released Debian. I don't think we can do it.

This leaves me with only one option. We have to deploy Bluez 4.101 headers to 11.10 machines.  It doesn't even have to be a full backport as the dependency is a compile time dependency.  My tests have shown that calling ::connect() with an extended sockaddr_l2 struct doesn't seem to cause any trouble on those older distros. 

Can we agree on that?

--
Alex