On Wed, Jun 15, 2016 at 05:05:21PM +0200, Klaas Freitag wrote:
With the ownCloud client we experience big problems in providing packages for the various distros, because of the huge variety of library versions out there on the different distros, in our case mainly Qt.
We are forced to maintain the client code to work even with Qt 4.6 (yes, not longer supported from Qt project), only because of old distros like Ubu 14 LTS (or even CentOS), which is still widely used.
And it's not only versions, its also patch sets. We have couple of patches against Qt which we a) would have to maintain for all the versions out there, and b) convince the distros to ship the patches. A LOT of work...
For our win and mac builds, we build and ship exactly one Qt version, built with our patch set. I hate to say it, but it is way harder for us to properly support Linux than Mac or Windows, for the described reasons. It wouldn't be even possible if we hadn't OBS, so thanks for that.
That hopefully illustrates why the idea of snappy appears overly useful from that POV. A lot of 3rdparty vendors do other dirty tricks such as static linking etc.
As far as I'm concerned, this reasoning rather illustrates what exactly is utterly and terribly _wrong_ with the concept of snap. Michal Kubeček -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org