5,705
edits
Changes
Jump to navigation
Jump to search
Documentation Team/Obsolete/Services Binary Services HOWTO (view source)
Revision as of 11:43, 15 January 2010
, 11:43, 15 January 2010Created page with '<noinclude> {{TOCright}} Category:Activity Team </noinclude> Work flow for services that require compilation stage: * create local initial service.info by invoking ''0sugar…'
<noinclude>
{{TOCright}}
[[Category:Activity Team]]
</noinclude>
Work flow for services that require compilation stage:
* create local initial service.info by invoking ''0sugar init'', tweak newly created ''service/service.info'' file
* provide relevant value for ''build-command'' field in ''service.info'' file
* if you want to support binaries for different dependencies environments, add additional sections to ''service.info'' file with ''requires'' fields that describe dependencies versions of particular environment
* increase/change version field in ''service.info'' file
* ''0sugar dist'' to add sources tarball to ''dist/'' and change local feed correspondingly
* on every platform, you are trying to support binaries for, run ''0sugar dist_bin'' to build, and add to local field, binaries for this particular platform
* if you added additional sections to ''service.info'', run ''0sugar dist_bin <section-name>'' in every environment, ''services.info'' has additional sections for
* ''0sugar push stable'' to rsync changed files from ''dist/'' to the server<br>see [[#Release workflows]] for other release scenarios
{{TOCright}}
[[Category:Activity Team]]
</noinclude>
Work flow for services that require compilation stage:
* create local initial service.info by invoking ''0sugar init'', tweak newly created ''service/service.info'' file
* provide relevant value for ''build-command'' field in ''service.info'' file
* if you want to support binaries for different dependencies environments, add additional sections to ''service.info'' file with ''requires'' fields that describe dependencies versions of particular environment
* increase/change version field in ''service.info'' file
* ''0sugar dist'' to add sources tarball to ''dist/'' and change local feed correspondingly
* on every platform, you are trying to support binaries for, run ''0sugar dist_bin'' to build, and add to local field, binaries for this particular platform
* if you added additional sections to ''service.info'', run ''0sugar dist_bin <section-name>'' in every environment, ''services.info'' has additional sections for
* ''0sugar push stable'' to rsync changed files from ''dist/'' to the server<br>see [[#Release workflows]] for other release scenarios