Difference between revisions of "0.100/Testing"
< 0.100
Jump to navigation
Jump to search
| Line 5: | Line 5: | ||
* Using a testing image (available for XO-1.5 and XO-4) | * Using a testing image (available for XO-1.5 and XO-4) | ||
* Using a 13.2.0 image and installing rpms. | * Using a 13.2.0 image and installing rpms. | ||
| − | * Using sugar- | + | * Using sugar-build |
=== Testing images === | === Testing images === | ||
| Line 40: | Line 40: | ||
And finally restart your computer. | And finally restart your computer. | ||
| + | |||
| + | === Using sugar-build === | ||
| + | |||
| + | Detailed instructions to use sugar-build are here [http://developer.sugarlabs.org/dev-environment.md.html] | ||
Revision as of 11:07, 16 October 2013
How test Sugar 0.100
We have different ways to test Sugar 0.100:
- Using a testing image (available for XO-1.5 and XO-4)
- Using a 13.2.0 image and installing rpms.
- Using sugar-build
Testing images
This images can be installed in XO without security enabled.
XO-4: | 33020xx4.zd
XO-1.5: PENDING UPLOAD
The olpc-os-builder configuration used to create these images is | here
Installing Sugar 0.100 testing rpms
As these are testing rpms, the version is 0.99. When we do the final release, will be changed to 0.100
The first step is install a13.2.0 image, downloaded | here
The second is create a file /etc/yum.repos.d/sugar99.repo with the following contents:
[sugar99] name=Sugar testing repository baseurl=http://dev.laptop.org/~gonzalo/sugar-99/ enabled=1
Later you need do:
rpm -e sugar-update-control yum update
If you want start fresh, and do not care about LOOSING EVERYTHING YOU HAVE IN YOUR JOURNAL, can do:
rm -rf .sugar
And finally restart your computer.
Using sugar-build
Detailed instructions to use sugar-build are here [1]