School Network/Open Build Service
Summary
This is a Sugar Labs instance of Open Build System (OBS) that is intended to be a:
- The place where software creators need to upload (directly or indirectly) sources to spread this software among the community.
- If uploaded software requires building phase, it will be automatically processed for all supported platforms.
- The resulting files will be accessible via sweets.sugarlabs.org and download.sugarlabs.org.
- The convenient instrument to create, using already uploaded software, 3rd party repositories with native packages for all supported GNU/Linux distributions.
The original OBS was patched to add Sweets support.
Sites
obs.sugarlabs.org
This is an API site, all OBS clients use it to get access to OBS. There is no need to work with site directly but it is possible.
Site uses HTTP Basic authentication. To get access, create 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 sweets command).
Introduction
For detailed information, read the original Open Build System documentation.
The content entities in OBS are:
- Projects, i.e., directories of Packages;
- Packages, that represent particular software projects.
Projects might be two types:
- top level, regular projects, like
baseorsdk; - user's home projects, like
~user/my-sugar-experiment.
Packages contain all files associated with particular software projects, e.g., tarballs with sweet sources for all versions that need to be shared.
Policy
Resources
- Open Build system home page.
- API specification.
- Downstream patch sources.