|
|
| Line 7: |
Line 7: |
| '''Blacklist Shell components''' | | '''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:
| | {{:Platform_Team/Sweets_Distribution/Features/Blacklists}} |
| | |
| <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''' |