Platform Team/Package Management System: Difference between revisions

Line 42:

* [http://download.sugarlabs.org/ Sugar Labs]'s resources to host various files.

The process departing point is a [[Activity Team/Zero Sugar/~~Service~~.info Specification|spec file]] which is used ~~by the {{Code|0sugar}} command~~ to accomplish two major tasks:

The process departing point is a [[Activity Team/Zero Sugar/0sugar.info Specification|spec file]] which is used within Zero Sugar to accomplish two major tasks:

* how to ~~build~~ the ~~application and its dependencies~~,

* how to prepare the code to launch,

* how to ~~deploy~~ the ~~application and its dependencies~~.

* how to share the code.

A building ~~step~~ might occur:

A preparation step might be not trivial only if code requires building stage. Building might occur:

* but, building is not required for scripting languages.

* on the developer's workstation, to deploy to environments similar to the developer's, or

* on OBS, to build for the GNU/Linux distributions that OBS supports.

~~Deployment~~ will ~~happen:~~

Sharing step might be:

* ~~via the 0install infrastructure:~~

* ''local'', if code needs to be run only in doer's environment.<br>Zero Sugar spec file will be handled as regular {{Code|activity.info}} file.

** ~~analogs~~ of ~~the application and its dependencies could~~ be ~~installed from native packaging system, if PackageKit is installed~~.

* ''peer-to-peer'', direct sharing between doer and users.

** by ~~downloading from http://download~~.~~sugarlabs~~.~~org/~~, if the ~~application was built in the developer's environment,~~

** Code can be launched if one of on-line users in Neighborhood View has a copy of shared code i.e. doer only needs to be on-line to let other people launch his code.

** ~~by downloading from OBS repositories, if~~ the ~~application was built on OBS~~,

** Just by transfering a bundle with the code e.g. using .xo bundles.

* via native packages, ~~only if the build happened on OBS; users need~~ to ~~follow the regular workflow~~, for ~~their distributions, to attach to the external OBS repository~~.

* ''client-server'', doer needs to upload code to the server and users will download it.<br>Particular method might be different:

** via the 0install infrastructure,

** via OBS repositories with native packages,

** by uploading bundles to servers like ASLO.

* ''distributor'', most likely similar to ''client-server'' but different from doer's point of view since only distributor is responsible for particular distribution method.

The regular workflow within Zero Sugar will look like:

@@ Line 42: / Line 42: @@
 * [http://download.sugarlabs.org/ Sugar Labs]'s resources to host various files.
-The process departing point is a [[Activity Team/Zero Sugar/Service.info Specification|spec file]] which is used by the {{Code|0sugar}} command to accomplish two major tasks:
+The process departing point is a [[Activity Team/Zero Sugar/0sugar.info Specification|spec file]] which is used within Zero Sugar to accomplish two major tasks:
-* how to build the application and its dependencies,
+* how to prepare the code to launch,
-* how to deploy the application and its dependencies.
+* how to share the code.
-A building step might occur:
+A preparation step might be not trivial only if code requires building stage. Building might occur:
-* but, building is not required for scripting languages.
 * on the developer's workstation, to deploy to environments similar to the developer's, or
 * on OBS, to build for the GNU/Linux distributions that OBS supports.
-Deployment will happen:
+Sharing step might be:
-* via the 0install infrastructure:
+* ''local'', if code needs to be run only in doer's environment.<br>Zero Sugar spec file will be handled as regular {{Code|activity.info}} file.
-** analogs of the application and its dependencies could be installed from native packaging system, if PackageKit is installed.
+* ''peer-to-peer'', direct sharing between doer and users.
-** by downloading from http://download.sugarlabs.org/, if the application was built in the developer's environment,
+** Code can be launched if one of on-line users in Neighborhood View has a copy of shared code i.e. doer only needs to be on-line to let other people launch his code.
-** by downloading from OBS repositories, if the application was built on OBS,
+** Just by transfering a bundle with the code e.g. using .xo bundles.
-* via native packages, only if the build happened on OBS; users need to follow the regular workflow, for their distributions, to attach to the external OBS repository.
+* ''client-server'', doer needs to upload code to the server and users will download it.<br>Particular method might be different:
+** via the 0install infrastructure,
+** via OBS repositories with native packages,
+** by uploading bundles to servers like ASLO.
+* ''distributor'', most likely similar to ''client-server'' but different from doer's point of view since only distributor is responsible for particular distribution method.
 The regular workflow within Zero Sugar will look like: