Moving Ubuntu SDK Plugin out of the QtCreator source package

[Sergey Shambir]

There are reasons to place headers in /usr/src instead of usual location.

All headers in /usr/include can be treated as stable APIs, and probably 
most developers expect that nobody will break /usr/include/foo.h in 
future distribution versions and updates. However, QtCreator headers 
contain many private APIs and many non-stable public APIs. As result, 
public API and ABI changes in each major, minor and patch version.

Actually QtCreator doesn't provide any external API: it splits all IDE 
subsystems to dynamically loadable modules in order to simplify 
development and make strict dependencies between subsystems. 3rd-party 
plugins are just 3rd-party modules binded to particular QtCreator 
version and build.

22.09.2013 12:09, Dmitry Shachnev пишет:
> On Wed, May 15, 2013 at 7:32 AM, Scott Kitterman <ubuntu at kitterman.com> wrote:
>> Although I didn't really explore the details, I understand that currently the
>> Ubuntu SDK QtCreator plugin has to have access to the QtCreator source to
>> build and that's why it is a patch in the qtcreator source package.
>>
>> Currently that is our only diff with upstream and Debian.  During this cycle,
>> could that be moved to it's own package?
> Looks like this is resolved now, but now we have a qtcreator-dev
> package shipping header files in /usr/src/ (sic!). It would be nice if
> a better location is chosen and the work is forwarded to Debian (or
> upstream).
>
> --
> Dmitry Shachnev
>