ubuntu-sdk-bugs team mailing list archive

[Benjamin Zeller <1456948@xxxxxxxxxxxxxxxxxx>]

While it would be techically possible to run the upgrades in the
background, it is not a good idea. When the access to the editor is
opened a developer can freely compile apps against a chroot that is
upgrading at the same time.

Imagine compiling a app against currently changing headers and
libraries. Best case is a failed compile step, worst case is a somehow
miscompiled application that behaves wrong and it is not possible to
debug why.  If a developer is willing to take that risk, he can manually
upgrade the chroots from the commandline.

** Changed in: qtcreator-plugin-ubuntu (Ubuntu)
       Status: New => Opinion

-- 
You received this bug notification because you are a member of Ubuntu
SDK bug tracking, which is subscribed to qtcreator-plugin-ubuntu in
Ubuntu.
https://bugs.launchpad.net/bugs/1456948

Title:
  Upgrading click chroot shall not block the user access to the editor

Status in qtcreator-plugin-ubuntu package in Ubuntu:
  Opinion

Bug description:
  Upgrading chroot takes quite a while, and it does not need to block
  user for other operations.

  UbuntuClickDialog blocked the user to access any features whiling it's
  doing Internal::UbuntuClickTool::Upgrade. However, upgrade a chroot
  should be safe to be running in the background like checking the
  updates in TargetUpgradeManager::checkForUpgrades.  I believe the
  clickDialog shall be set to Qt::WindowModal[1].

  [1] http://doc.qt.io/qt-5/qt.html#WindowModality-enum

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