← Back to team overview

compiz team mailing list archive

[Bug 1035261] Re: Port compiz to gsettings and consequently remove unity-2d


** Description changed:

  Porting compiz and so unity to gsettings has a lot of consequences:
  - compiz:
    * build with gsettings support
    * add migration scripts
+   * add xml files for the g-c-c integration (we used the metacity ones before)
  - unity :
    * gconf -> gsettings patches (2)
    * rebuild with the new gsettings compiz
    * add transitional packages for all unity-2d packages
    * add migration scripts
  - nux:
-   * remove the X11 Xsession.d detection script
+   * remove the X11 Xsession.d detection script
  - gnome-control-center:
   * should be ported in both the keyboard part by reverting the gsettings revert patch
   * in the unity background configuration panels to support gsettings
   * in the display configuration panels to support gsettings
  - gnome-settings-daemon to drop the gsettings revert patch:
  - metacity should be updated to >> 2.34.2 (gsettings integration, shared with compiz). Sync back with debian, demote to universe -> this forces us to drop a lot of patches to make unity-2d running
  - consequently, dropping unity-2d because of metacity patches won't be ported, and unity-2d isn't maintained to port from gconf to gsettings:. Removal from the archive
  - lightdm to transition people from unity-2d to unity-3d session
  - unity-greeter to drop hardware detection capability for nux
  - gnome-session to drop the unity-2d session and recommends
  - release-upgrader in precise to detect if the card can't run unity-3d, and if so, show a warning to tell to stay on the LTS
  - ubuntu-desktop seed to remove dep on unity-2d
  People forcing the upgrade or installing on a machine without hardware
  acceleration will then use unity with llvmpipe.

You received this bug notification because you are a member of compiz
packagers, which is subscribed to compiz in Ubuntu.

  Port compiz to gsettings and consequently remove unity-2d

To manage notifications about this bug go to: