Difference between revisions of "Talk:Taxonomy"

From Sugar Labs
Jump to: navigation, search
(New page: ==Operating System and Sugar stacking== The block diagram contains Ribose as part of the operating system, whilst it is defined as: > Ribose is the set of hardware-centric software compo...)
 
(Operating System and Sugar stacking)
Line 13: Line 13:
  
 
In fact part of the stack is defined as a 'Sugar environment, ready to be installed through a package manager' in other sections of the document, clearly making these elements platform agnostic [see: http://wiki.sugarlabs.org/go/Taxonomy#Sucrose:_The_interface.2C_plus_a_set_of_demonstration_activities].
 
In fact part of the stack is defined as a 'Sugar environment, ready to be installed through a package manager' in other sections of the document, clearly making these elements platform agnostic [see: http://wiki.sugarlabs.org/go/Taxonomy#Sucrose:_The_interface.2C_plus_a_set_of_demonstration_activities].
 +
 +
Ludovic F

Revision as of 07:39, 17 May 2008

Operating System and Sugar stacking

The block diagram contains Ribose as part of the operating system, whilst it is defined as:

> Ribose is the set of hardware-centric software components that have been developed
> throughout this project. It includes the XO kernels, OHM, any init-script customizations,
> etc. Ribose should be construed as including all components necessary to boot the system,
> enough to install Glucose if it has not yet been installed

Why this discrepancy?

IMO the Ribose definition is XO orientated (biased?) and this would make the software stack more complex to understand if we have to define it based on the hardware it runs on.

In fact part of the stack is defined as a 'Sugar environment, ready to be installed through a package manager' in other sections of the document, clearly making these elements platform agnostic [see: http://wiki.sugarlabs.org/go/Taxonomy#Sucrose:_The_interface.2C_plus_a_set_of_demonstration_activities].

Ludovic F