Difference between revisions of "Sweets Distribution"

From Sugar Labs
Jump to navigation Jump to search
(Obsolete with reason)
 
(13 intermediate revisions by 3 users not shown)
Line 1: Line 1:
[[Image:Question.png|65px|link=Sweets_Distribution/Logo]]
+
{{Obsolete | This was a sort of "Sugar LTS" project by [[User:alsroot]] that has been abandoned}}
 +
 
 +
<span class="linkgroup">[[File:Question.png|65px|link=Sweets_Distribution/Logo]]</span>
  
 
{{Template:Sweets Distribution Linkbar}}
 
{{Template:Sweets Distribution Linkbar}}
Line 7: Line 9:
 
== Summary ==
 
== Summary ==
  
This is a set of repositories with native packages that compose [[Platform_Team/Harmonic_Distribution/Software|Basic software]] of [[Platform_Team/Harmonic_Distribution|Harmonic Distribution]] effort.
+
This is a set of 3rd party repositories with Sugar Learning Platform packages for major GNU/Linux [[Sweets_Distribution/Supported_platforms|distributions]].  
  
This is a special, Sugar only, distribution. These are the key points that make the Sweets Distribution different from other [[Community/Distributions|Distributions]]:
+
The major reasons to support all these repositories are:
  
* The Sweets Distribution is formed as a 3rd party repository, i.e., it is not a complete GNU/Linux distribution;
+
* Let people to try new functionality which is not available from the regular sources;
* It supports [[Platform_Team/Harmonic_Distribution/Supported_platforms|several]] GNU/Linux distributions, and their releases, at the same time;
+
* Support GNU/Linux distributions that lack of Sugar Learning Platform from official repositories;
* Packages from these repositories do not interfere with the rest of the system, e.g., it is possible to use Sugar from the Sweets Distribution and Sugar from official repositories at the same time.
+
* Bring recent Sugar Learning Platform versions to systems initially released with older Sugar.
  
 
== Repositories ==
 
== Repositories ==
  
Sweets Distribution is formed as a [[Template:Sweets_Distribution_Linkbar|list of repositories]] that can be added to the system. Only one repository can be registered in the system at the same time. Repositories are identified by names and might be in stable or development stage. Different repositories might be available on different platforms from the Harmonic Distribution [[Platform_Team/Harmonic_Distribution/Supported_platforms|supported platforms list]].
+
Sweets Distribution is formed as a [[Template:Sweets_Distribution_Linkbar|list of repositories]] that can be added to the system. Only one repository can be registered in the system at the same time. Repositories are identified by names and might be in stable or development stage. Different repositories might be available on different platforms from the [[Sweets_Distribution/Supported_platforms|supported platforms list]].
  
 
== Installation ==
 
== Installation ==
Line 35: Line 37:
 
type the following commands in a terminal:
 
type the following commands in a terminal:
  
  wget ftp://download.sugarlabs.org/packages/sweets-distribution.sh
+
  wget http://download.sugarlabs.org/packages/sweets-distribution.sh
 
  sudo sh sweets-distribution.sh
 
  sudo sh sweets-distribution.sh
  
Line 42: Line 44:
 
  sweets-distribution status
 
  sweets-distribution status
  
*To add chosen, here {{Code|Factory}}, repository in the system
+
*To add chosen, here {{Code|0.94}}, repository in the system
  
  sudo sweets-distribution select Factory
+
  sudo sweets-distribution select 0.94
  
 
=== Install packages ===
 
=== Install packages ===
Line 52: Line 54:
 
In the regular way for your operating system (such as with '''apt-get install''' or '''yum install'''), from a local system terminal, console, or via SSH, install one of the following packages:
 
In the regular way for your operating system (such as with '''apt-get install''' or '''yum install'''), from a local system terminal, console, or via SSH, install one of the following packages:
  
* {{Code|sweets-desktop}}<br>The full set of packages from Sweets Desktop;
+
* {{Code|sweets-desktop}}<br>The full set of packages from Sweets Desktop.
 
 
* {{Code|sweets-sugar}}<br>Only the Sugar Shell.
 
  
 
Sometimes, it may be required to downgrade packages while switching to another repository. The easy way to do so is with the {{Code|sync}} command:
 
Sometimes, it may be required to downgrade packages while switching to another repository. The easy way to do so is with the {{Code|sync}} command:
Line 86: Line 86:
 
=== Sweets Desktop session ===
 
=== Sweets Desktop session ===
  
If {{Code|sweets-desktop}} package was installed, it will be possible to log in to a Sweets Desktop session:
+
If {{Code|sweets-desktop}} package was installed, it will be possible to log in to a Sweets Desktop session. Choose the ''Sweets Desktop'' session type in a login manager.
 
 
* On an XO laptop (only for Factory repository). From within an original Sugar session, go to the Control Panel and select the Sweets Distribution component, then enable the ''Sweets Desktop is default Sugar session'' switch. Switching back is accomplished the same way.
 
* On regular desktops. Choose the ''Sweets Desktop'' session type in login manager.
 
  
 
=== Run Sugar in a window ===
 
=== Run Sugar in a window ===
  
 
To run Sugar in a window without logging out from the current desktop environment, select the ''Education/Sugar'' application menu item or enter the following command in a terminal:
 
To run Sugar in a window without logging out from the current desktop environment, select the ''Education/Sugar'' application menu item or enter the following command in a terminal:
 
 
  sweets-sugar-emulator
 
  sweets-sugar-emulator
 +
=== [[The_Undiscoverable#sugar-emulator.2C_sugar-runner_and_sweets-sugar-emulator|Run Sugar full screen]] ===
 +
Run this command in a terminal or edit the properties of the menu item for ''Sugar''
 +
sweets-sugar-emulator -f, --fullscreen
  
 
=== Sugar Activities ===
 
=== Sugar Activities ===
Line 104: Line 103:
 
* The rest of activities need to be handled manually, e.g., manual installing missed dependencies.
 
* The rest of activities need to be handled manually, e.g., manual installing missed dependencies.
  
The Factory repository should bring [[Platform_Team/Harmonic_Distribution/Software#Distribution_via_Sugar_Network|different design]] solutions for handling Sugar Activities. That will make the whole Sugar Activities related experience more reliable and smooth.
+
All other repositories should bring [[Sugar Network]] integration, a different design solution for handling Sugar Activities. [[Sugar Network]] is assumed to improve the process of launching Sugar Activities to make it more reliable and smooth. By default, Sugar Network integration might be switched off, [[Platform_Team/Sweets_Distribution/0.94:SugarNetwork#Sugar_Network_integration|enable]] it after installation.
 
 
=== Experimental features ===
 
 
 
{{Note/warning|Caution|Factory repository is not intended for regular usage. It exists only for testing purposes.}}
 
 
 
To try the development version, use the {{Code|Factory}} repository. The Factory repository provides the most recent development version of Harmonic Distribution [[Platform_Team/Harmonic_Distribution/Factory#Features|features]].
 
 
 
If something looks broken, try to upgrade to recent packages and if problem still remains, please, [[#Feedback|contact us]].
 
  
 
== Testing ==
 
== Testing ==

Latest revision as of 17:50, 18 May 2016

Stop hand.png NOTE:
The content of this page is considered
DEPRECATED and OBSOLETE
It is preserved for historical research, along with its talk page.

This was a sort of "Sugar LTS" project by User:alsroot that has been abandoned


Question.png

Sweets Distribution repositories: | 0.88 | 0.94 | 0.94:SugarNetwork | Factory |

These are overview and usage pages regarding the Sweets Distribution. Read technical pages for getting detailed information.

Summary

This is a set of 3rd party repositories with Sugar Learning Platform packages for major GNU/Linux distributions.

The major reasons to support all these repositories are:

  • Let people to try new functionality which is not available from the regular sources;
  • Support GNU/Linux distributions that lack of Sugar Learning Platform from official repositories;
  • Bring recent Sugar Learning Platform versions to systems initially released with older Sugar.

Repositories

Sweets Distribution is formed as a list of repositories that can be added to the system. Only one repository can be registered in the system at the same time. Repositories are identified by names and might be in stable or development stage. Different repositories might be available on different platforms from the supported platforms list.

Installation

The installation occurs in two phases:

  • add one of Sweets Distribution repositories to local system;
  • install packages from added Sweets Distribution repository.

Add repository

Experienced users might follow manual instructions to add Sweets Distribution repositories to the system.

For easy attaching Sweets Distribution repositories, use sweets-distribution command.

If sweets-distribution is not yet installed, download the sweets-distribution.sh install script and run it from the root user, e.g., type the following commands in a terminal:

wget http://download.sugarlabs.org/packages/sweets-distribution.sh
sudo sh sweets-distribution.sh
  • To get the status information about currently selected and all available repositories:
sweets-distribution status
  • To add chosen, here 0.94, repository in the system
sudo sweets-distribution select 0.94

Install packages

When the sweets-distribution select command finishes, the local system will be aware of the Sweets Distribution repository and it will be possible to install packages.

In the regular way for your operating system (such as with apt-get install or yum install), from a local system terminal, console, or via SSH, install one of the following packages:

  • sweets-desktop
    The full set of packages from Sweets Desktop.

Sometimes, it may be required to downgrade packages while switching to another repository. The easy way to do so is with the sync command:

sudo sweets-distribution sync

Most of the Sweets Distribution packages will be placed in the /opt/sweets directory; thus, it will be possible to use Sugar from the Sweets Distribution and from official packages at the same time.

Usage

Below are instructions on how to use the Sweets Distribution after installing packages.

Sweets Desktop session

If sweets-desktop package was installed, it will be possible to log in to a Sweets Desktop session. Choose the Sweets Desktop session type in a login manager.

Run Sugar in a window

To run Sugar in a window without logging out from the current desktop environment, select the Education/Sugar application menu item or enter the following command in a terminal:

sweets-sugar-emulator

Run Sugar full screen

Run this command in a terminal or edit the properties of the menu item for Sugar

sweets-sugar-emulator -f, --fullscreen

Sugar Activities

For stable 0.94 and 0.88 repositories, the following points are assumed:

  • Fructose activities need to be used only from Sweets Distribution packages, at least for ones that have external dependencies, i.e., they should not be upgraded from the Activity Library;
  • The rest of activities need to be handled manually, e.g., manual installing missed dependencies.

All other repositories should bring Sugar Network integration, a different design solution for handling Sugar Activities. Sugar Network is assumed to improve the process of launching Sugar Activities to make it more reliable and smooth. By default, Sugar Network integration might be switched off, enable it after installation.

Testing

See also

Feedback

  • Submit your bug report or feature request.
  • Subscribe to the sugar-devel mailing list and email with the subject prefixed with [SWEETS].
  • Ask your question on IRC channels, #sugar (not logged) or #sugar-newbies (logged).