<div><div>Hello, my name is Alvar Maciel, from Buenos Aires Argentina and I am contacting you for different reasons. I would like to learn more about Sugar and the procedures that are needed to be folowed in order to make that tuquito (<a href="http://tuquito.org.ar/" target="_blank">http://tuquito.org.ar</a> this is an ubuntu derivated distribution) takes part of the distributions that are officially supported by sugar. I would like to tell you our case, and what we have done until now 1. Necessity <div class="gmail_quote"><div>Classmate netbooks has been chosen in some provinces of Argentine and in the "Conectar Igualdad Plan" (<a href="http://www.conectarigualdad.gob.ar/" target="_blank">http://www.conectarigualdad.gob.ar/</a>). These computers will have distributions based on Ubuntu. One of the problems the users of ubuntu are facing is that the packages of sugar are not up to date or we have problems to compile the hulahop seccion and we have errors executing the browse activity because of the updating of xulrunner . </div> <div>2. Solutions considering the situation that we have with the people of Tuquito, we have decided to try to solve these problems and compile sugar from jhbuild. You can see on these links 2 tickets created by me relating to this job (<a href="http://bugs.sugarlabs.org/ticket/2496" target="_blank">http://bugs.sugarlabs.org/ticket/2496</a> <a href="http://bugs.sugarlabs.org/ticket/2629" target="_blank">http://bugs.sugarlabs.org/ticket/2629</a>). 3. Procedures that we have followed to compile sugar in Tuquito (can be applied in ubuntu 10.10 too) first step: In /sugar-jhbuild/sjhbuild/sysdeps.py add the following line Line 18: 'Tuquito': 'unstable', in line 53 we add 'Tuquito' Line 53: elif name in ['ubuntu', 'debian','Tuquito']: second step add 3 files to ~/sugar-jhbuild/config/sysdeps using the xml for ubuntu <div>cp 50ubuntu-10.10.xml 50tuquito-4.1.xml cp 50ubuntu-allversions.xml 50tuquito-allversions.xml cp 10ubuntu-allversions.xml 10tuquito-allversions.xml</div> third step add the next packages to solve dependecies to compile </div><div><div>libgtk2.0-dev libdbus-glib-1-dev libxml2-dev libpopt-dev python-dev libtool intltool python-gconf python-gnome2-dev python2.7-dev python-gtk2-dev python-gnome2-dev libgnome-desktop-dev libgnomecups1.0-dev libwnck-dev librsvg2-dev gtk-doc-tools libtelepathy-glib-dev libasound2-dev icon-slicer xulrunner-dev libcroco3-dev libtelepathy-glib-dev icon-naming-utils shtool libgconf2-dev abiword espeak espeak-data libabiword-2.8-dev libtelepathy-glib0 libdbus-glib-1-dev metacity pep8 pylint python-abiword python-evince python-rsvg python-telepathy python-wnck python-xklavier telepathy-gabble telepathy-salut xulrunner-1.9.2 python-lxlm y python-beautifulsoup </div>forth step: We have built a package to solve the xulruner problem. Here you can find the package<a href="http://acercadelaeducacion.com.ar/scripts/python_xpcom" target="_blank"> http://acercadelaeducacion.com.ar/scripts/python_xpcom</a> with this procedure we are able to compile the sugar from jhbuild in tuquito (in theory works in ubuntu 10.10 too) A Question: I have done this with short knowledge of sugar and with a lot of help from the local chapter of sugarlabs (sugarlabs Argentina). Our aim would be to officially reach the support of sugar in Tuquito. <ul><li>Which procedure should we follow to be an official distribution for sugar?</li></ul>Next Steps In order to test this version of sugar I have done a script that builds the package (sugar-jhbuild) and the sugar.desktop in /usr/share/applications. This script also makes the xssesion to execute the sugar-emulator in full screen mode. We would also like to make a version of Tuquito and sugar in which the users could choose the enviroment to start the computer (gnome or sugar and not the sugar-emulator). Could you explain us how to do this? You can see the script here <a href="http://www.acercadelaeducacion.com.ar/scripts/script_sugar_tuquito.sh" target="_blank">http://www.acercadelaeducacion.com.ar/scripts/script_sugar_tuquito.sh</a> Best regards Alvar </div></div> </div></div>