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

From Sugar Labs
Jump to navigation Jump to search
Line 11: Line 11:
  
 
This repository with stable Sucrose-0.94 packages built on [[Platform_Team/Harmonic_Distribution/Supported_platforms#Map|supported platforms]].
 
This repository with stable Sucrose-0.94 packages built on [[Platform_Team/Harmonic_Distribution/Supported_platforms#Map|supported platforms]].
 
== 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 {{Code|/etc/sugar/blacklist}} directory. The blacklist might be overridden by {{Code|/etc/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'''
 
 
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 {{Code|/desktop/sugar/user/default_nick}} GConf key to {{Code|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 {{Code|/schemas/desktop/sugar/show_register}} GConf key to {{Code|true}}.
 
 
'''Closer integration with login managers'''
 
 
Sugar Shell will reuse language setting from GDM manager, [http://bugs.sugarlabs.org/ticket/2603 #2603].
 
  
 
== Sources ==
 
== Sources ==
Line 72: Line 29:
  
 
{{:Platform_Team/Sweets_Distribution/Feedback}}
 
{{:Platform_Team/Sweets_Distribution/Feedback}}
 +
 +
== Subpages ==
 +
 +
{{Special:PrefixIndex/{{PAGENAMEE}}/}}

Revision as of 02:22, 28 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.

To start using it, follow the instructions:

Summary

This repository with stable Sucrose-0.94 packages built on supported platforms.

Sources

Gitorious repositories with sources are hosted in the following projects:

Look for the master-0.94 git branches in source repositories.

See also

Feedback

  • Submit your bug report or feature request.
  • Subscribe to the sugar-devel mailing list and email with the subject prefixed with [SWEETS].
  • Ask your question on IRC channels, #sugar (not logged) or #sugar-newbies (logged).

Subpages