5,705
edits
Homepage | Activities | Events | Lists | Development | Translate | Contact
Changes
Jump to navigation
Jump to search
Line 25:
Line 25: + + Line 46:
Line 48: + + + +
Platform Team/Guide/Sweets Packaging (view source)
Revision as of 04:59, 24 December 2009
, 04:59, 24 December 2009→service.info file
Service publishing work flow 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 publishing work flow 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'' section ===
Service.info file should contain at least ''[Service]'' section:
Service.info file should contain at least ''[Service]'' section:
* ''build-requires'', what services should be installed before building service from sources
* ''build-requires'', what services should be installed before building service from sources
build-requires = <service-name> [<not-before-version>[-<before-version>]] [; ...]
build-requires = <service-name> [<not-before-version>[-<before-version>]] [; ...]
=== ''Buildtime'' section ===
=== ''Distro:'' sections ===
Service.info file could contain other sections for various binary implementations. These sections are intended to describe particular dependencies environment and should contain only ''requires'' fields e.g if service developer is going to support binary implementations for f9 and f11, ''[F9]'' and ''[F11]'' sections will contain requires fields with dependencies versions that are used in f9 and f11. Names of these fields will be used in ''dist_bin'' command of ''0sugar-publish'' application.
Service.info file could contain other sections for various binary implementations. These sections are intended to describe particular dependencies environment and should contain only ''requires'' fields e.g if service developer is going to support binary implementations for f9 and f11, ''[F9]'' and ''[F11]'' sections will contain requires fields with dependencies versions that are used in f9 and f11. Names of these fields will be used in ''dist_bin'' command of ''0sugar-publish'' application.