[Development] Basing Qt Creator Coding Style on C++ Core Guidelines?

Lisandro Damián Nicanor Pérez Meyer perezmeyer at gmail.com
Tue Nov 22 18:31:05 CET 2016


On lunes, 21 de noviembre de 2016 17:20:09 ART Thiago Macieira wrote:
> On segunda-feira, 21 de novembro de 2016 21:23:54 PST Lisandro Damián
> Nicanor
> Pérez Meyer wrote:
> > Now I have a question: how will the Qt community take that a distro
> > changes
> > the SONAME of a lib from, let's say, 5 to 5abi1 when that kind of changes
> > happen?
> 
> We prefer to work with downstreams and have those changes in Qt itself. Not
> because we don't trust Debian, Fedora and OpenSUSE maintainers to do the
> right thing, but precisely because it's multiple teams. Why should each
> team redevelop the solution?

Ah, I was not clear enough, I was actually meaning this: having a solution 
pre-thought right from Qt itself. And yes, what you describe seems an 
excellent way to deal with this.

-- 
Lisandro Damián Nicanor Pérez Meyer
http://perezmeyer.com.ar/
http://perezmeyer.blogspot.com/
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: This is a digitally signed message part.
URL: <http://lists.qt-project.org/pipermail/development/attachments/20161122/06bbcedb/attachment.sig>


More information about the Development mailing list