On Thu, Nov 27, 2008 at 4:45 PM, Erik Blankinship <[EMAIL PROTECTED]> wrote: > Perhaps address how Activity authors might need to handle / work > around the different distro specifics on one page, unless the goal is > to have different activity releases per distro.
Yeah, that's an interesting subject. We have control on the sugar api, in other words, what activity authors can expect to find that is specific to sugar. But activities use lots of other, non-sugar, software like libraries, X, etc How can activity authors know what their activities can expect in the environments they are run in? One notable example: many activities developed for the XO depend on pygame, but I'm not sure it's properly packaged for all distros, and even then, activities installed as .xo won't be dragging it along. How can we give a better experience here? Regards, Tomeu > On 11/27/08, Walter Bender <[EMAIL PROTECTED]> wrote: >> I think the distro-specific issues should be delegated to the >> individual distro pages. The Supported Systems page is a bit of a >> tangle right now. Anyone have time to do a reorg? >> >> -walter >> >> On Thu, Nov 27, 2008 at 4:09 AM, Morgan Collett >> <[EMAIL PROTECTED]> wrote: >>> On Thu, Nov 27, 2008 at 02:06, Edward Cherlin <[EMAIL PROTECTED]> wrote: >>>> On Wed, Nov 26, 2008 at 2:33 PM, Luke Faraone <[EMAIL PROTECTED]> wrote: >>>>> On Wed, Nov 26, 2008 at 17:07, Edward Cherlin <[EMAIL PROTECTED]> >>>>> wrote: >>>>>> >>>>>> [EMAIL PROTECTED]:~$ sugar-emulator >>>>>> Traceback (most recent call last): >>>>>> File "/usr/bin/sugar-emulator", line 22, in <module> >>>>>> from emulator import main >>>>>> File "/usr/share/sugar/shell/emulator.py", line 31, in <module> >>>>>> from sugar import env >>>>>> ImportError: No module named sugar >>>>> >>>>> Edward, this is not a Sugar problem, please ask about it on the >>>>> sugar-ubuntu >>>>> mailing list. >>>> >>>> We need a Wiki page with a detailed statement of which bugs and >>>> support questions go on which lists. I think that the current setup >>>> works fine for the developers working in each of the projects >>>> involved, but is hopeless for others, especially newcomers. >>> >>> I agree. I'm not sure where such a page should go - on the supported >>> systems page? On the page for each distro? >>> >>> The plan for Ubuntu is that you should log bugs in the Ubuntu >>> bugtracker, https://launchpad.net - for example, >>> https://bugs.launchpad.net/ubuntu/+source/sugar for Sugar itself. >>> Please log your issue there so we can track it. >>> >>>>> In any case, how did you install sugar, exactly? It works fine for me on >>>>> a >>>>> fresh intrepid install. >>>> >>>> I had Sugar installed, and I upgraded to Intrepid. There was one >>>> dependency error that required me to do a manual package installation, >>>> replacing sugar-datastore with python-olpc-datastore, IIRC. >>> >>> That is a known issue which still needs fixing, ubuntu-sugarteam... >>> >>> Regards >>> Morgan >>> _______________________________________________ >>> Sugar mailing list >>> [email protected] >>> http://lists.laptop.org/listinfo/sugar >>> >> >> >> >> -- >> Walter Bender >> Sugar Labs >> http://www.sugarlabs.org >> _______________________________________________ >> Sugar mailing list >> [email protected] >> http://lists.laptop.org/listinfo/sugar >> > _______________________________________________ > Sugar mailing list > [email protected] > http://lists.laptop.org/listinfo/sugar > _______________________________________________ Sugar mailing list [email protected] http://lists.laptop.org/listinfo/sugar
