Sugar on OpenSolaris
By user9149671 on Mar 21, 2010
Sugar on OpenSolaris
In my spare time over the past six months, I have been working to get the OLPC desktop called Sugar working on OpenSolaris. The Sugar environment is the worl'd best desktop designed for children, so now it is available for use by people using OpenSolaris. I have written or updated about 50 spec-files, so that OpenSolaris users can easily build it and try it out. To build the spec-files you need to download the spec-files from spec-files-extra, and use the CBE (Common Build Environment) and simply run the following command:
$ pkgtool --download --autodeps build SFE\*sugar\*.spec
These spec-files should build Sugar well on any fairly recent OpenSolaris or Solaris SXCE/SXDE release. However, some Sugar programs are not working fully and I have not yet finished porting all programs. For example, I have not yet ported the Sugar web browser. So, it would be great if other interested people wanted to get involved and help out.
To help me with this process, I made a request to the OLPC Contributor's Program for two XO 1.5 laptops to help me with the porting effort and this was recently approved on March 12th. I will continue posting blog entries to keep people posted with my progress. Following is the proposal that I submitted:
1. Project Title & Shipment Detail
Name of Project: Sugar on OpenSolaris
Number of Laptops (or other hardware) You Request to Borrow:
Loan Length—How Many Months:
1 or 2 XO-1.5 laptops for 1 year.
2. Team Participants
Name(s) & Contact Info: Brian Cameron
Employer and/or School: Sun Microsystems and the GNOME Foundation
I have been working on the Sun Desktop team for the past 9 years
and have spent several weeks porting Sugar so it runs on
I am a director of the GNOME Foundation and am involved with
working on GNOME Marketing and have an interest in improving
cross-marketing and organizational opportunities between GNOME
Project Objectives: Making Sugar Available on OpenSolaris.
I have already spent several weeks porting about 75% of the
Sugar platform to OpenSolaris. You can find the dozens of
SFEsugar\* spec-files that I have already created here:
However, many programs do not seem to work, or seem to have
errors when running. Since the Sugar emulator is not supported
for OpenSolaris, I cannot use it for testing the platform.
Having 1 or 2 XO-1.5 units would assist me in this porting
effort by allowing me to become more familiar with how the
Sugar platform works on a system that fully supports it already.
Two units would be most useful since it would enable me to
learn how to use the networking features more easily.
My goal is to make Sugar fully functional on OpenSolaris and
to make the Sugar packages available to OpenSolaris users via
a package repository. This will expose Sugar to new users and
developers and will also provide needed software useful for
children available to OpenSolaris users.
4. Plan of Action
I have already ported much of the Sugar platform to OpenSolaris
and plan to have the Sugar desktop fully ported and available to
end users via an OpenSolaris package repository within the next
year. Having the XO-1.5 units will assist me in making sure that
the functionality is as similar as possible to the intended user
Why is this project needed?
Enabling the OpenSolaris community to get involved with Sugar
will expose the Sugar platform to a broader set of users and
I would prefer 2 machines so that I can familiarize myself with
how the platform works with networking features.
Will you consider (1) salvaged/rebuilt or (2) damaged XO
I cannot use the emulator because it is not available for
Salvaged/rebuilt machines would be fine, though I would prefer
the XO-1.5 units if possible.
6. Sharing Deliverables
Project URL—where you'll report specific ongoing progress:
I will report progress on my work blog:
I am also happy to report progress on any other forums or
websites if requested.
Please web-publish this entire completed proposal, removing any sections affecting your personal privacy. Ask if you want help!
How will you convey tentative ideas & results back to the OLPC/Sugar community, prior to completion?
Via the appropriate sugar or olpc developer mailing lists.
How will the final fruits of your labor be distributed to children or community members worldwide?
Via a public OpenSolaris package repository. This will likely
be the "contrib" repository initially.
Will your work have any possible application or use outside our community?
If yes, how will these people be reached?
Yes, making packages available to OpenSolaris users will make
the Sugar platform more visible and available to a new set of
Have you investigated working with nearby XO Lending Libraries or Project Groups?
Would your Project benefit from Support, Documentation and/or Testing people?
I will likely need to work with the Sugar development community
to assist me in resolving issues. For example, I know that work
is needed to make OLPC support audio and network management on
OpenSolaris since the frameworks for these are different.
Teachers' input into Usability?
I don't anticipate working directly on usability issues.
How will you promote your work?
Via my blog and through the GNOME Foundation.
Can we help you with an experienced mentor from the OLPC/Sugar community?
Yes, if possible.
If YES: specify the kind of Ongoing Mentoring that will benefit you most.
A Sugar developer who can help me understand how to address
8. Timeline (Start to Finish)
Please include a Proposed timeline for your Project life-cycle: (this can be in the form of Month 1, Month 2, etc rather than specific dates)
Include a couple milestones, even if tentative.
I plan to make available the Sugar desktop to OpenSolaris users
within 6 months. However, I anticipate it will take another 6
months to work out any remaining issues to provide an acceptable
Specify how you prefer to communicate your ongoing progress and obstacles!
Via my blog, or whatever mechanisms you prefer.
[x] I agree to pass on the laptop(s) to a local OLPC group or other interested contributors in case I do not have need for the laptop(s) anymore or in case my project progress stalls.