Difference between revisions of "Sugar Network/Recipe Specification"

From Sugar Labs
Jump to navigation Jump to search
(work on English)
Line 4: Line 4:
 
</noinclude>
 
</noinclude>
  
Service publishing workflow is similar to activities. There is an info file, here service/service.info, which describes current status(not history) of development process. All these fields, finally, go to feed file while publishing new version. Service.info file is an analog of scenario files in regular GNU/Linux distributions like .spec files in RPM.
+
The Service publishing workflow is similar to activities. There is an info file, here service/service.info, which describes the current status (not history) of the development process. All these fields, finally, go to a feed file when publishing a new version. The service.info file is an analog of scenario files in regular GNU/Linux distributions, like .spec files in RPM.
  
See last version on [http://git.sugarlabs.org/projects/0sugar/repos/mainline/blobs/master/service.info.example].
+
See the latest version at [http://git.sugarlabs.org/projects/0sugar/repos/mainline/blobs/master/service.info.example].

Revision as of 23:46, 6 March 2010


The Service publishing workflow is similar to activities. There is an info file, here service/service.info, which describes the current status (not history) of the development process. All these fields, finally, go to a feed file when publishing a new version. The service.info file is an analog of scenario files in regular GNU/Linux distributions, like .spec files in RPM.

See the latest version at [1].