Difference between revisions of "Activity Team/Obsolete/Services Shell"
| Line 27: | Line 27: | ||
== Detailed Description == | == Detailed Description == | ||
| − | This service provides sugar shell itself and API for activities that need to treat with shell e.g. to get some useful information about sugar environment | + | This service provides sugar shell itself and dbus API for activities that need to treat with shell e.g. to get some useful information about sugar environment. |
| − | |||
| − | |||
== Dependencies == | == Dependencies == | ||
Revision as of 10:18, 10 January 2010
Summary
The Sugar shell.
Contacts
Current status
| Branch [1] | Sugar Platforms | Support status/Notes |
|---|---|---|
| 0 | 0.82-1.00 | is comming |
Detailed Description
This service provides sugar shell itself and dbus API for activities that need to treat with shell e.g. to get some useful information about sugar environment.
Dependencies
What other services or 0install packages depend on this service? Are there changes outside the developers' control on which completion of this service depends? In other words, does your service depend on completion of another service owned by someone else or that you would need to coordinate, which might cause you to be unable to finish on time? Other upstream projects like Python?
Documentation
Is there upstream documentation on this service, or notes you have written yourself? Has this topic been discussed in the mailing list or during a meeting? Link to that material here so other interested developers can get involved.
If auto-documentation field is set in service.info file, API documentation will be generated on this page:
How To Test
Activity Team/Obsolete/Services Shell/Testing