[Development] Summary of renaming changes

[Thiago Macieira]

On sexta-feira, 19 de outubro de 2012 09.27.42, Poenitz Andre wrote:
> - The "problem" only exists on Linux 
>    * There are existing, working solutions to the "problem" there
>    * There are skilled people (distro packagers) there perfectly 
>       capable of handling the "problem" 
>    * The majority of Qt users is not affected at all.
> 
> - The "solution" is invasive.
>    * Some of the follow-up changes are only triggered by the renaming
>      E.g. the "need" to co-install lupdate does not exist yet, but is 
>      introduced by the qmake changes.
>    * It affects any user project setup involving moc, uic, etc "custom
>      buildstep", like the ones all Qt using Visual Studio projects have,
>      therefore eliminating the possibilty of having a code base running
>      on both Qt 4 and Qt 5, and even hampering a direct Qt 4 -> Qt 5 port.
>   * Documentation needs to be adjusted.
>   * Existing third party documentation of Qt in use, howto's, tutorials, 
>     in the *net lose value, because it will be not accurate anymore.

Please add this factor into your analysis, then:

Packagers WILL rename and there will be installations with renamed tools.

How does that affect the documentation? How does that affect the existing 
setups? How does that tutorials, etc.?

-- 
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/20121019/4bbc0d59/attachment.sig>