[Development] Co-installation & library naming rules

[Thiago Macieira]

On quinta-feira, 11 de outubro de 2012 21.09.24, Oswald Buddenhagen wrote:
> On Thu, Oct 11, 2012 at 11:54:28AM -0700, Thiago Macieira wrote:
> > I'd simply version the libraries.
> 
> yes. me too. i wouldn't rename them, though. ;)
> 
> > We already do that on Windows too, for example.
> 
> only because windows has no built-in support for versioning dlls.
> and fwiw, what qmake does is an utter hack which causes trouble on a
> regular basis.

Kill two birds with one stone: remove the hacks by inserting the "5" into the 
actual name.

> your whole argument is built on the premise that the system-provided
> versioning is broken enough that we should ignore it and just claim that
> different major versions are different libraries alltogether.

It's not broken. What I'm saying is that the rules we've followed so far are 
insufficient. They need to be amended for source-incompatible and co-installable 
libraries.

> i disagree with this premise.
> and i dislike what consequences it has for everything else which is not
> a library, and the effect it has on *me*, a qt developer.

The only tools that need renaming are the tools that are run by users but are 
tied to a specific library version. That's basically qmake.

If we had a generic build tool that worked with multiple Qt versions (like 
cmake), we wouldn't need to do it. Since our tool hardcodes Qt specifics and is 
not backwards compatible with older versions, we need to. That was our 
decision.

Most of the other tools can go unrenamed: they'll either be in libexec because 
they're not run directly by the user, or they're end-user applications that 
retain compatibility (creator, qdbus, assistant, linguist and its tools, 
etc.). The only exceptions are tools that load plugins, like designer, and 
even then, one could argue that the same .ui should work with either uic.

-- 
Thiago Macieira - thiago.macieira (AT) intel.com
  Software Architect - Intel Open Source Technology Center
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 190 bytes
Desc: This is a digitally signed message part.
URL: <http://lists.qt-project.org/pipermail/development/attachments/20121011/eaadb463/attachment.sig>