5,705
edits
Changes
Jump to navigation
Jump to search
Line 70:
Line 70: − + − The ways how upstream project might be obtained:+ − − * Sources − * Third party repositories with binary packages for particular GNU/Linux distribution − − The downstream organizations can choose the most practical way, eg, by using upstream repositories, adding new binary packages and creating final installation images.
Platform Team/Server Kit/Architecture (view source)
Revision as of 11:27, 9 June 2011
, 11:27, 9 June 2011→Distribution
Except just having binary packages, it should be possible to build downstream packages and final OS images on http://packages.sugarlabs.org using only its web UI. The resulted files will be accessible for download from http://download.sugarlabs.org. It is [https://build.opensuse.org/ Open Build Service] based service to build packages and images for rpm and deb based GNU/Linux distributions.
Except just having binary packages, it should be possible to build downstream packages and final OS images on http://packages.sugarlabs.org using only its web UI. The resulted files will be accessible for download from http://download.sugarlabs.org. It is [https://build.opensuse.org/ Open Build Service] based service to build packages and images for rpm and deb based GNU/Linux distributions.
== Distribution ==
== Deployment model ==
It is entirely downstream decision how to deploy Sugar Server based solutions.
== Components ==
== Components ==