5,705
edits
Changes
Jump to navigation
Jump to search
Line 35:
Line 35: − + + + + + + + + + + + +
Platform Team/Guide/Sweets Packaging (view source)
Revision as of 14:15, 19 December 2009
, 14:15, 19 December 2009→0sugar-publish tool
0alias 0sugar-publish http://download.sugarlabs.org/services/0sugar-publish/feed.xml
0alias 0sugar-publish http://download.sugarlabs.org/services/0sugar-publish/feed.xml
While working, ''0sugar-publish'' creates ''dist/'' directory in project root and uses it as a rsynced copy of service's directory on the server. So, you need ssh access to sunjammer server, create ticket for ''shell.sugarlabs.org'' category on http://bugs.sugarlabs.org/.
While working, ''0sugar-publish'' creates ''dist/'' directory in project's root and uses it as a rsynced copy of service's directory on the server. So, you need ssh access to sunjammer server, create ticket for ''shell.sugarlabs.org'' category on http://bugs.sugarlabs.org/.
''0sugar-publish'' commands are:
* ''init'', get feed file from the server and place it to dist/
* ''fetch'', rsync entirely dist/ from the server
* ''dist'', dist source or any arch implementation
* ''dist_bin'', dist binary implementation
* ''push'', rsync dist/ to the server
* ''lint'', check feed file on the server
The regular work flow after increasing version/stability in ''service.info'' file, is invoking one of ''dist*'' command to change local feed in ''dist/'' and place there tarballs, then invoke ''push'' command to rsync changed files to the server.