Difference between revisions of "Platform Team/Sweets Distribution/0.94"

From Sugar Labs
Jump to navigation Jump to search
Line 18: Line 18:
 
A part of Telepathy related code was rewritten to try to minimize regressions from Glucose-0.88 code. The goal is to make Shell's Telepathy related functionality the same level stable as it was in 0.88 before total redesigning Telepathy related code.
 
A part of Telepathy related code was rewritten to try to minimize regressions from Glucose-0.88 code. The goal is to make Shell's Telepathy related functionality the same level stable as it was in 0.88 before total redesigning Telepathy related code.
  
'''Blacklist activity updater'''
+
'''Blacklist Shell components'''
  
Sweets Distribution provides Fructose activities. The ones that depend on not trivial dependencies should be used only from native packages. To not let Control panel activity updater install new versions of such activities, it looks for black list files in {{Code|/usr/share/sugar/activities.blacklist}} directory. Files should contain bundle_id values per line. For all these activities, new versions will be ignored in Control panel activity updater. The black list might be overridden by {{Code|/usr/share/sugar/activities.whitelist}} directory files.
+
To make downstream distributing more flexible, Sweets Distribution provides functionality to blacklist usage of particular Shell components. The blocking rules should be place to arbitrary files to {{Code|/usr/share/sugar/blacklist}} directory. The blacklist might be overridden by {{Code|/usr/share/sugar/whitelist}} directory files. Each line in blacklist/whitelist files should contain one rule in format:
 +
 
 +
<CATEGORY> <COMPONENT>
 +
 
 +
Where the {{Code|CATEGORY}} is a type of Shell components and {{Code|COMPONENT}} is an item within the catogory:
 +
 
 +
* '''cpsection'''<br>Control panel sections, components should be directory names from {{Code|/usr/share/sugar/extensions/cpsection}};
 +
 
 +
* '''deviceicon'''<br>Device icon, components should be {{Code|.py}} file names from {{Code|/usr/share/sugar/extensions/deviceicon}} directory;
 +
 
 +
* '''globalkey'''<br>Global key handler, components should be {{Code|.py}} file names from {{Code|/usr/share/sugar/extensions/globalkey}} directory;
 +
 
 +
* '''updater'''<br>Ignore activities while launching activity updates from ''Software update'' Control panel section, components should bundle_id values. For example, Sweets Distribution might provide Fructose activities, the ones that depend on not trivial dependencies should be used only from native packages.
 +
 
 +
# Example of blacklist file
 +
 +
updater    org.laptop.WebActivity  # Depends on broken xulrunner package
 +
cpsection  sweets                  # Downstream distributions do not need it
 +
deviceicon battery.py              # Broken on my system
 +
globalkey  viewsource.py            # Аt the same time...
  
 
'''Disabled reusing of system users while registration'''
 
'''Disabled reusing of system users while registration'''

Revision as of 11:04, 27 April 2012

Sweets Distribution repositories: | 0.88 | 0.94 | 0.94:SugarNetwork | Factory |

This page collects information directly associated with the Sweets Distribution repository 0.94.

Summary

This repository with stable Sucrose-0.94 packages.

Features

The list of major features that this repository has, on top of pristine Sucrose, with information how to configure them.

Improved Telepathy related code

A part of Telepathy related code was rewritten to try to minimize regressions from Glucose-0.88 code. The goal is to make Shell's Telepathy related functionality the same level stable as it was in 0.88 before total redesigning Telepathy related code.

Blacklist Shell components

To make downstream distributing more flexible, Sweets Distribution provides functionality to blacklist usage of particular Shell components. The blocking rules should be place to arbitrary files to /usr/share/sugar/blacklist directory. The blacklist might be overridden by /usr/share/sugar/whitelist directory files. Each line in blacklist/whitelist files should contain one rule in format:

<CATEGORY> <COMPONENT>

Where the CATEGORY is a type of Shell components and COMPONENT is an item within the catogory:

  • cpsection
    Control panel sections, components should be directory names from /usr/share/sugar/extensions/cpsection;
  • deviceicon
    Device icon, components should be .py file names from /usr/share/sugar/extensions/deviceicon directory;
  • globalkey
    Global key handler, components should be .py file names from /usr/share/sugar/extensions/globalkey directory;
  • updater
    Ignore activities while launching activity updates from Software update Control panel section, components should bundle_id values. For example, Sweets Distribution might provide Fructose activities, the ones that depend on not trivial dependencies should be used only from native packages.
# Example of blacklist file

updater    org.laptop.WebActivity   # Depends on broken xulrunner package
cpsection  sweets                   # Downstream distributions do not need it
deviceicon battery.py               # Broken on my system
globalkey  viewsource.py            # Аt the same time...

Disabled reusing of system users while registration

In pristine Sucrose, this feature is enabled by default. That means that system user will be reused as Sugar nickname while Sugar initial startup. To revert original behavior, set /desktop/sugar/user/default_nick GConf key to system.

Registration on school servers is disabled by default

Sugar Shell support registration on OLPC XS school server. Sweets distribution does not provide OLPS XS and this functionality is disabled by default. To revert original behavior, set /schemas/desktop/sugar/show_register GConf key to true.

Closer integration with login managers

Sugar Shell will reuse language setting from GDM manager, #2603.