School Network/Open Build Service: Difference between revisions

Line 3:

This is a [http://git.sugarlabs.org/0sugar/build-service patched] Sugar Labs instance of [http://openbuildservice.org/ Open Build System] (OBS) that is intended to be a:

* ~~Hosting~~ sources and ~~making~~ binaries, if there is need, for [[Platform_Team/Sweets|Sweets]].

* Place to host sources and to make binaries, if there is need, for [[Platform_Team/Sweets|Sweets]].

* Convenient instrument to create 3rd party repositories with native packages for all [[#Supported_platforms|supported]] GNU/Linux distributions.

Line 12:

=== obs.sugarlabs.org ===

This is an [https://obs.sugarlabs.org/apidocs/ API] site, all OBS clients use it to get access to OBS. There is no need to work with site directly but it is [http://en.opensuse.org//openSUSE:Build_Service_Curl possible].

This is an [https://obs.sugarlabs.org/apidocs/ API] site, all OBS clients use it to get access to OBS. There is no need to work with the site directly, but that is [http://en.opensuse.org//openSUSE:Build_Service_Curl possible].

~~Site~~ uses HTTP Basic authentication. To get access, [[Service/Account#Sugar_Labs_Central_Login|create]] Sugar Labs Central Login account.

The site uses HTTP Basic authentication. To get access, [[Service/Account#Sugar_Labs_Central_Login|create]] a Sugar Labs Central Login account.

=== packages.sugarlabs.org ===

This is an original OBS Web client. It is intended to be used only by people who need to create native packages, i.e., not for most of Sugar developers. But, until ~~creating~~ more appropriate tool for Sugar needs, it is the only ~~one~~ Web client to manage already released software (~~the releasing is~~ being processed by [[Platform_Team/Guide/Sweets_Packaging#Releasing|sweets command]]).

This is an original OBS Web client. It is intended to be used only by people who need to create native packages, i.e., it is not needed for most Sugar developers. But, until a more appropriate tool is created for Sugar needs, it is the only Web client available to manage already released software (those released by being processed by the [[Platform_Team/Guide/Sweets_Packaging#Releasing|sweets command]]).

== Content ==

The ~~contend~~ on OBS might be several kinds:

The content on OBS might be of several kinds:

=== Projects ===

Projects are directories of Packages and might be two types:

Projects are directories of Packages and might be of two types:

* top level, regular projects, like {{Code|base}} or {{Code|sdk}};

Line 35:

Packages represent particular software projects and contain all files associated with these projects, e.g., tarballs with sources.

There are several types of ~~package~~ supported on OBS:

There are several types of packages supported on OBS:

* packages that represent sweets,

* native packages based on sweets,

* native packages ~~with~~ using sweet recipes as spec files,

* native packages using sweet recipes as spec files,

* aliases,

* regular OBS packages.

Line 47:

=== Repositories ===

Every project has repositories to build its packages against. Repositories might be two types:

Every project has repositories to build its packages against. Repositories might be of two types:

* inherited from another project;

* initial repositories, aka downloaded-on-demand, that are associated with particular GNU/Linux distribution release;

* initial repositories, aka, downloaded-on-demand, that are associated with a particular GNU/Linux distribution release;

* {{Code|sweets.sugarlabs.org}} repository should present if Packages need to be distributed via Zero Install.

* {{Code|sweets.sugarlabs.org}} repository should be present if Packages need to be distributed via Zero Install.

Every repository has supported architectures, e.g., {{Code|i586}} or {{Code|x86_64}}. There is also special architecture, {{Code|0install}}, only for {{Code|sweets.sugarlabs.org}}.

Every repository has supported architectures, e.g., {{Code|i586}} or {{Code|x86_64}}. There is also the special architecture, {{Code|0install}}, only for {{Code|sweets.sugarlabs.org}}.

== Supported platforms ==

@@ Line 3: / Line 3: @@
 This is a [http://git.sugarlabs.org/0sugar/build-service patched] Sugar Labs instance of [http://openbuildservice.org/ Open Build System] (OBS) that is intended to be a:
-* Hosting sources and making binaries, if there is need, for [[Platform_Team/Sweets|Sweets]].
+* Place to host sources and to make binaries, if there is need, for [[Platform_Team/Sweets|Sweets]].
 * Convenient instrument to create 3rd party repositories with native packages for all [[#Supported_platforms|supported]] GNU/Linux distributions.
@@ Line 12: / Line 12: @@
 === obs.sugarlabs.org ===
-This is an [https://obs.sugarlabs.org/apidocs/ API] site, all OBS clients use it to get access to OBS. There is no need to work with site directly but it is [http://en.opensuse.org//openSUSE:Build_Service_Curl possible].
+This is an [https://obs.sugarlabs.org/apidocs/ API] site, all OBS clients use it to get access to OBS. There is no need to work with the site directly, but that is [http://en.opensuse.org//openSUSE:Build_Service_Curl possible].
-Site uses HTTP Basic authentication. To get access, [[Service/Account#Sugar_Labs_Central_Login|create]] Sugar Labs Central Login account.
+The site uses HTTP Basic authentication. To get access, [[Service/Account#Sugar_Labs_Central_Login|create]] a Sugar Labs Central Login account.
 === packages.sugarlabs.org ===
-This is an original OBS Web client. It is intended to be used only by people who need to create native packages, i.e., not for most of Sugar developers. But, until creating more appropriate tool for Sugar needs, it is the only one Web client to manage already released software (the releasing is being processed by [[Platform_Team/Guide/Sweets_Packaging#Releasing|sweets command]]).
+This is an original OBS Web client. It is intended to be used only by people who need to create native packages, i.e., it is not needed for most Sugar developers. But, until a more appropriate tool is created for Sugar needs, it is the only Web client available to manage already released software (those released by being processed by the [[Platform_Team/Guide/Sweets_Packaging#Releasing|sweets command]]).
 == Content ==
-The contend on OBS might be several kinds:
+The content on OBS might be of several kinds:
 === Projects ===
-Projects are directories of Packages and might be two types:
+Projects are directories of Packages and might be of two types:
 * top level, regular projects, like {{Code|base}} or {{Code|sdk}};
@@ Line 35: / Line 35: @@
 Packages represent particular software projects and contain all files associated with these projects, e.g., tarballs with sources.
-There are several types of package supported on OBS:
+There are several types of packages supported on OBS:
 * packages that represent sweets,
 * native packages based on sweets,
-* native packages with using sweet recipes as spec files,
+* native packages using sweet recipes as spec files,
 * aliases,
 * regular OBS packages.
@@ Line 47: / Line 47: @@
 === Repositories ===
-Every project has repositories to build its packages against. Repositories might be two types:
+Every project has repositories to build its packages against. Repositories might be of two types:
 * inherited from another project;
-* initial repositories, aka downloaded-on-demand, that are associated with particular GNU/Linux distribution release;
+* initial repositories, aka, downloaded-on-demand, that are associated with a particular GNU/Linux distribution release;
-* {{Code|sweets.sugarlabs.org}} repository should present if Packages need to be distributed via Zero Install.
+* {{Code|sweets.sugarlabs.org}} repository should be present if Packages need to be distributed via Zero Install.
-Every repository has supported architectures, e.g., {{Code|i586}} or {{Code|x86_64}}. There is also special architecture, {{Code|0install}}, only for {{Code|sweets.sugarlabs.org}}.
+Every repository has supported architectures, e.g., {{Code|i586}} or {{Code|x86_64}}. There is also the special architecture, {{Code|0install}}, only for {{Code|sweets.sugarlabs.org}}.
 == Supported platforms ==