Changes

Jump to navigation Jump to search
no edit summary
Line 32: Line 32:  
  http://services.sugarlabs.org/<service>/<subservice>.xml
 
  http://services.sugarlabs.org/<service>/<subservice>.xml
   −
The Sugar Services maintainer process is to use the [[#0sugar_tool|0sugar]] tool to create the proper feeds and tarballs. 0sugar uses a spec file service/service.info as an scenario file (like .spec files in RPM). See also [[Documentation_Team/Services/Service.info_Specification|specification]] of service.info files.
+
The Sugar Services maintainer process is to use the [[Documentation_Team/Services/0sugar|0sugar]] tool to create the proper feeds and tarballs. 0sugar uses a spec file service/service.info as an scenario file (like .spec files in RPM). See also [[Documentation_Team/Services/Service.info_Specification|specification]] of service.info files.
 
  −
== 0sugar tool ==
  −
 
  −
To start developing services, install injector and 0sugar tools:
  −
 
  −
* Install the [http://download.sugarlabs.org/services/zeroinstall-injector/bundles/zeroinstall-injector-latest.sh latest version] of patched zeroinstall-injector, see also 0install [http://0install.net/injector-using.html|tutorials] for more 0install-related information.
  −
 
  −
* Tweak the PATH environment variable, and after executing the command, you need to relogin.
  −
echo 'PATH=~/.local/bin:$PATH' >> ~/.bashrc
  −
 
  −
* Register 0sugar alias
  −
0alias 0sugar http://services.sugarlabs.org/0sugar
  −
 
  −
While working, 0sugar creates the .0sugar directory, which is a cache directory, and should not be included in version control system repositories. It has the following hierarchy:
  −
 
  −
* .0sugar/remote, rsynced copy (could be partial) of the service directory on the server,
  −
* .0sugar/local, directory with output tarballs after invoking dist and build commands,
  −
* .0sugar/(src|build|dist) directories after invoking the build command.
  −
 
  −
During a maintenance session, 0sugar will create result files in .0sugar/remote directory that will be rsynced to the server by a push command, therefore, a shell account on sunjammer server is required, to get one, follow these [[Sysadmin/Shell_account_request|instructions]].
      
== Versioning scheme ==
 
== Versioning scheme ==

Navigation menu