Changes

Platform Team/Guide/Sweets Packaging (view source)

Revision as of 12:59, 6 June 2010

1,411 bytes removed , 12:59, 6 June 2010

→‎Versioning scheme

Line 36: Line 36:

* Read ''service.info'' file [[Documentation_Team/Services/Service.info_Specification|specification]]

and follow the rest of this document instruction about development details.

−

~~== Versioning scheme ==~~

−

~~There could be two different versioning schemes for services.~~

−

~~=== Upstream versions ===~~

−

If the service is just a wrapper around an existing project with its own versioning scheme, then there is no need in even any mentioning of versions in the service.info file. The particular version will be chosen on every ''0sugar dist*'' command invocation or will be fetched from native packaging systems (if the service doesn't provide binaries and [[Documentation Team/Services/Native packages usage|only]] contains information about software already well-packaged in various GNU/Linux distributions).

−

~~=== Native versions ===~~

−

~~The rest of services will use this scheme:~~

−

~~<version>-<revision>~~

−

* <version> is a ''version'' field from the service.info file which is a plain number.

−

* <revision> is an auto-incremented number, which is changed by the ''0sugar push'' command (like Subversion revision).

−

~~The commands ''dist'' and ''dist_bin'' rewrite releases with the same ''version'' versions and don't remove other releases.~~

−

[[#Library_section|Libraries]] have also an ''age'' parameter which is a [http://www.gnu.org/software/libtool/manual/html_node/Libtool-versioning.html#Libtool-versioning libtool]-like age version part. ''age'' won't be exposed in version string, but will be present in feed files, and 0sugar will check it while deciding what dependency version should be chosen.

== Stability status ==

Alsroot

Bots, Bureaucrats, Check users, Administrators, Widget editors

5,705

edits