Re: [Sugar-devel] Sugar Dashboard: Needs testing

2019-06-11 Thread Hrishi Patel
Thanks. A few have been solved. I will try to fix the rest soon. On Tue, Jun 11, 2019 at 2:27 PM James Cameron wrote: > Tested on OLPC OS, and issues opened. > > -- > James Cameron > http://quozl.netrek.org/ > ___ Sugar-devel mailing list

Re: [Sugar-devel] Problem packaging toolkit

2019-06-11 Thread James Cameron
No, configure.ac already installs for both versions, you just have to run it twice. This is how other projects handle mixed version environment. You would have seen that had you looked through the other packages as I suggested. ;-) On Ubuntu 18.04 there are no more than 260 of those packages

Re: [Sugar-devel] Sugar Dashboard: Needs testing

2019-06-11 Thread James Cameron
Tested on OLPC OS, and issues opened. -- James Cameron http://quozl.netrek.org/ ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel

Re: [Sugar-devel] Video: The Coolest Netbook You’ve Forgotten About: The OLPC XO-1

2019-06-11 Thread Sumit Srivastava
Watch the comments, I tried to help. :P On Tue, 11 Jun 2019, 4:31 am James Cameron, wrote: > Thanks Ignacio, > > I like the Prius in the background. > > I like how my updates to the OLPC web site were visible. Makes it > worth the effort. ;-) > > Software shown was from February 2008; with

[Sugar-devel] Sugar Dashboard: Needs testing

2019-06-11 Thread Hrishi Patel
Hello, Sugar Dashboard is near completion. It'd be great if anyone can test it and provide issues, feedback, bugs, etc. before we release it. The link to repository: https://github.com/sugarlabs/Dashboard.Activity You can open issues on the repository. Thanks. Regards

Re: [Sugar-devel] Problem packaging toolkit

2019-06-11 Thread ANIKET MATHUR
Thanks. Regarding packaging for both the version, first we have to make changes in the configure.ac file so that the toolkit is installed for both the versions automatically? For Python 3 do I have to make a separate repo or just push the python3-sugar3 to the *current repo?* Sorry, I am confused.