Sugar Creation Kit/sck/Advanced Topics

<-BACK to Sugar Creation Kit

Sweets Distribution

Sugar Network Tutorial

• Annotated screen shots with Links

Sweets-Getting Started

Click on title ^ to go to topic

• Some ideas on how to present SWEETS. (Inkyfingers)
• look at Infrastructure for an overview.

Sweets Distribution

Click on title ^ to go to topic

(Sweets Distribution is easier to use for Ubuntu' and its Derivatives (Adding an additional Repository to apt) as the packages are pre-configured, ready to use.)

• Community/Distributions/Sweets_Distribution

(Developed for Trisquel-sugar-Toast )

Sweets

Click on title ^ to go to topic

(Advanced)

Debian, Ubuntu, Fedora, Mandriva, openSUSE, and Gentoo

• Sweets Usage
• Sugar via Sweets

(This guide describes how to run Sugar using Sugar Packaging Management System, Sweets.)

Request for better Documentation of installs

Log of Installation of sugar-sweets 0.88 and 0.94 on f16-GNOME3-shell

Installing_Sugar_via_sweets_-_in_Mint-12

Installing_Sugar_via_sweets_-_in_Debian_testing_Wheezy

• sweets packaging

(For developers)

Sugar Network

Click on title ^ to go to topic

• Overview: Sugar_Network/Concept

Collaboration support for Internet-less environments (but not only)

• Sugar Network Activities when f8 key is pressed

Tests of which activities start by page

Harmonic_Distribution

• Look at this tutorial: Sugar_Network/Tutorial

* The possibility to launch Base Software in heterogeneous
  software and hardware environments.
* Using Base Software, provide access to various Content
  (Sugar activities, artifacts created by Sugar activities, books, etc.)
  created within the Sugar community.
* Using Base Software, provide collaborative functionality to
  support Social activity around the Content.
* Instruments and workflows to adapt Content and Base Software
  to specific needs that Sugar Deployment might face,
  including extreme ones like off-line environments and restricting
  hardware.

• [Sugar-devel] [SWEETS] Testing collaboration related fixes 05/07/2012

Hi all!
Following the plan for Harmonic Distribution v0.2 (which will be a basis
for Sugar Distribution to use in peruvian pilot), in Sugar Shell code
were made fixes that are intended to make Telepathy (everything related to
Neighbourhood view and Sugar Activities sharing/joining) more stable
(that was broken since global redesign started after 0.88 release).
Fixes are accessible from SweetsDistribution:Factory repository. Follow
regular Sweets Distribution installation instructions[1] to install
fixed Sugar Shell on all supported platforms[2].
Some visible changes in F1 view:
* the number of buddies should be increased from ~20 to 70-90
  some Sugar versions (maybe 0.90-0.92) don't publish information about
  nickname/colors on regular basis; this information are being stored on
  disk for now
* for some buddies, server still don't have information about colors
  (replaced by gray) and nick names (jabber ids)
If you have a time and want to help Puno deployment pilot, please,
consider possibility to install sweets-desktop from Factory repository
and do some testing of collaboration functionality.

Some tips:

* while interacting with another buddies, make sure that all
  participants use Sweets Distribution (some F1 buddies might misbehave)
* the good criteria of stability level of new Sugar is comparing with
  how collaboration happen in 0.88 Sugar.
Source code, for interested in people, can be found in top commits from:

* http://git.sugarlabs.org/desktop/sugar
* http://git.sugarlabs.org/desktop/sugar-toolkit
* http://git.sugarlabs.org/server/prosody-sugar
[1] Community/Distributions/Sweets_Distribution#Installation
[2] Platform_Team/Harmonic_Distribution/Supported_platforms

-- Aleksey
Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel

BoxGrinder

BoxGrinder Build is an easy to use command line tool to create appliances (virtual images) from simple plaintext appliance definition files. BoxGrinder can produce appliances for a variety of virtual and cloud platforms using plugins supporting technologies such as VMware or EC2.

• http://boxgrinder.org
• http://boxgrinder.org/community/
• http://boxgrinder.org/tutorials/
• http://boxgrinder.org/tutorials/boxgrinder-build-meta-appliance/
• http://boxgrinder.org/download/boxgrinder-build-meta-appliance/

Pungi

Advanced

• used to build non-live CD/DVD isos

Pungi needs to run on the arch it is composing, as root, and with an install of what it is composing, eg if you are composing Fedora 8, you need to be running Fedora 8.
This is so that the correct userland tools are used to create the images and such used by anaconda.
The eventual usage of pungi will most likely be in mock chroots to facilitate this.
It needs to run on the arch it is composing due to how anaconda-runtime determines what files to put in the boot images at this time.
Currently the releases of pungi are designed to run on an updated Rawhide system. Development of pungi always tracks Rawhide.

Koji

Click on title ^ to go to topic

(Very Advanced)

Koji is the software that builds RPM packages for the Fedora project

How_to_create_an_RPM_package

• How_to_create_an_RPM_package in Fedora

https://fedoraproject.org/wiki/How_to_create_an_RPM_package

Git

Click on title ^ to go to topic

Advanced - Used by Sugar Developers

• Git Tutorial
• L10n Translations

There is a git user named "pootle" that acts as the proxy by which all
PO file translations are committed from the Pootle server.  Please
make pootle a committer on the repo and I will make the connections
between git and the Pootle server.
Some "best practices" about working with git and Pootle are described here.
 Translation Team Best Practices

groupthink

Click on title ^ to go to topic

• Very Advanced

"Groupthink is a library of self-sharing data structures written in python and shared over dbus.

Together with the D-Bus Tubes provided by the Telepathy framework, this enables data structures to be shared over a network."

OLPC XO-1 and XO-1.5 links and Notes

Click on title ^ to go to topic

Dextrose Building

Dextrose uses olpc-os-builder, a tool create by OLPC to build official and customized system images.
The Dextrose git repository contains, olpc-os-builder, local customizations specific to Dextrose,
and fixes and enhancements waiting to be pushed upstream. 

• Dextrose/Building

XS Schoolserver 0.7

Click on title ^ to go to topic

• How to install:http://wiki.laptop.org/go/XS_Installing_Software_0.7
• Download: http://dev.laptop.org/xs/OLPC-School-Server-0.7beta2-i386.iso

Manuals

OLPC Manual

Help Activity Refresh

Manuals Info

ARM

References

http://fedoraproject.org/wiki/Architectures/ARM

http://fedoraproject.org/wiki/Architectures/ARM/Fedora_17_Beta

https://fedoraproject.org/wiki/Architectures/ARM/Fedora17_rawhide

http://dl.fedoraproject.org/pub/fedora-secondary/releases/test/17-Beta/Images/armhfp/

Boot from CD: http://www.trimslice.com/forum/viewtopic.php?f=25&t=412

http://developer.nvidia.com/tegra-2-technical-reference-manual

Ubuntu 11.04

Updates TrimSlicePro

• use terminal

apt-get update
apt-get dist-upgrade

Updated to Linux-image-trimslice 2.6.38.3-1.03 5183 kb

Install sugar 0.90

apt-get install sugar-emulator-0.90

• Long update

fedora-arm

f17 Nightly Images

• Serial interface ONLY
• Note these are experimental FOR TESTING ONLY - Still in development; use with caution
• The kernel used does not support startx

No graphical interfaces are available at this time for TrimSlicePro and TrimSlice -h

• dd will write a live USB but it will not boot in arm devices.

works in intel PC's

• livecd-tools does not work

Nightly Composes: http://scotland.proximity.on.ca/arm-nightlies/

Most of the SD card images can be used with a USB storage device drive using the following method:
Write the image to both the USB storage device and an SD card. IE, write the image using xzcat file.xz > /dev/sdX then xzcat file.xz > /dev/mmcblkX.
Once written, use a partition editor such as fdisk to delete the VFAT partition from the USB drive and the Linux partition from SD card.
Plug the SD and USB storage into your ARM device and power up. 
The ARM system will load any applicable bootloader pieces, kernel, and initramfs from the SD card, but use the USB storage for the root filesystem.

Nearly images are self-sufficient, but a kernel tarball is optionally available with the contents of the image's /boot and /lib/modules directories.
These can be used in conjunction with the tarball root filesystems to create your own images.

Resizer

• Resizer Script and systemd file

http://scotland.proximity.on.ca/arm-nightlies/vault/mknightly.tar.xz

PPC

Power PC

• Community/Distributions/Ubuntu/PPC
• http://fedoraproject.org/wiki/Architectures/PowerPC

  Latest Fedora release for PPC is currently Fedora 12

Doing builds again for fedora 16

• IRC: #fedora-ppc on irc.freenode.net

Sugar Patches

http://patchwork.sugarlabs.org/project/sugar/list/

son)