Difference between revisions of "Deployment Platform/Blacklist Shell Components"
Jump to navigation
Jump to search
(Created page with "== Summary == To make deployment distribution more flexible, Sweets Distribution provides functionality to blacklist usage of particular Shell components. The reason for such...") |
m (Alsroot moved page Deployment Platform/Shell Blacklists to Deployment Platform/Blacklist Shell Components without leaving a redirect) |
(One intermediate revision by the same user not shown) | |
(No difference)
|
Latest revision as of 03:33, 12 June 2013
Summary
To make deployment distribution more flexible, Sweets Distribution provides functionality to blacklist usage of particular Shell components. The reason for such blacklisting is that otherwise, the only way is removing unneeded Shell components from the installation directory, i.e., upstream packages need to be patched or post-install procedures should be processed. Blacklisting makes it possible to reuse upstream Shell packages as-is and change only local client configuration.
Blocking rules
The blocking rules should be placed to [blacklist] configuration section. Each section item blacklists particular Shell component:
deviceicon
Space separated list of python files, from deviceicon directory, to disable corresponding device icons;cpsection
Space separated list of directory names, from cpsection directory, to disable corresponding Control Panel sections;globalkey
Space separated list of python files, from globalkey directory, to disable corresponding global keys.