touch-packages team mailing list archive

[Timo Jyrinki <timo.jyrinki@xxxxxxxxxxxxx>]

I've pushed branches for those that compile just fine without the
private headers.

For ubuntu-settings-components and ubuntu-keyboard, is it correct that
you're only using the private headers for tests and not anything that
gets installed into packages?

That would explain why they are not picking up the flag of using private
symbols. You can mark this Won't Fix if you can't get around using the
private stuff in tests. And thank you for not using them in the main
software!

But if you can find anything in eg. Qt 5.4 to get around your
QWindowSystemInterface::registerTouchDevice usage, that would be nice.
Or, convincing upstream to make it public. I also found
https://bugreports.qt.io/browse/QTBUG-26647 at least.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ubuntu-keyboard in Ubuntu.
https://bugs.launchpad.net/bugs/1427991

Title:
  Stop build-depending on private Qt headers

Status in ubuntu-keyboard package in Ubuntu:
  New
Status in ubuntu-push-qml package in Ubuntu:
  New
Status in ubuntu-settings-components package in Ubuntu:
  New
Status in ubuntu-system-settings package in Ubuntu:
  New

Bug description:
  Your package is build-depending on either qtbase5-private-dev or
  qtdeclarative5-private-dev, but it does not seem to use any symbols
  marked as private. Even if it would use private headers, please
  consider stopping using those since there may be incompatible changes
  in future Qt versions.

  Depend only on the qtbase5-dev and/or qtdeclarative5-dev.

  The reason for this bug is to both limit private headers usage and to
  keep better track of the users.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-keyboard/+bug/1427991/+subscriptions