[Sugar-devel] [SoaS] Sugar on Fedora looking forward

James Cameron quozl at laptop.org
Wed Jul 11 19:52:22 EDT 2018

On Wed, Jul 11, 2018 at 09:35:47AM +0100, Peter Robinson wrote:
> Hello All,
> This is intended to ask questions and seek feedback.
> I've not really had time to deal with Sugar for some time, but it also
> doesn't tend to take up a lot of time so it's not been a major
> problem, we glue it together when it breaks etc.
> Kalpa has done a good job keeping most of the Activities up to date.
> But there's a number of things that are getting to the point where
> they'll need action or they'll break so I'd like to gather details
> from the Sugar community what their plans are here to see if it's
> worthwhile continuing the Fedora support of Sugar.
> 1) gstreamer 1.0 support in Activies. The 0.10 series is well and
> truly dead and unmaintained, but there's a couple of key Activities
> that still depend on it. Clock and Record are the two big ones here.
> Are there any plans to move them to gst1?

They were moved.  Check the release announcements and the tarball


> 2) GTK2 sugar-toolkit, again a number of Activities still haven't
> moved to gtk3, any plans?

Yes.  We have a contributor working on that now, so please make sure
we know which ones Fedora think are still GTK+ 2.  Time critical.

> 3) eToys, we've not shipped this by default for some time, I plan on
> retiring it and any of it's dependencies in Fedora 29. Good riddance
> sugar-presence-service!

I've no news on this one.  Best to contact Etoys project.

> 4) This is the big one... python2. With python2 being EOL real soon
> now is there any interest in moving to py3, I know there was some work
> years ago to do some readiness here with the move to gtk3 but I don't
> remember the details. Fedora is actively moving to python3 and has
> been for some years, I think for at least 6 releases it's been
> possible to run without py2 installed at all. Is this the nail in the
> coffin for Sugar?

Our port to Python 3 is going well.  We have good working code in pull
requests and branches, and plan to merge it once we have the critical
components complete.  Our plan is in the GitHub projects tab for the

Your downstream transition plan can be one of;

- package sugar-toolkit-gtk3 as both Python 2 and Python 3, so that
  Python 3 activities can be packaged, and so that Python 2 packages
  you have now need not be rushed into Python 3,

- package sugar-toolkit-gtk3 as only Python 3, and make sure all your
  Python 2 activity packages are either dropped or ported to Python 3.

> Also with my note above about time and the points in between are there
> still people interested in Sugar on Fedora? Anyone interested enough
> to assist?

I agree, downstreams need help, it's a big job to keep this

> Peter
> _______________________________________________
> SoaS mailing list
> SoaS at lists.sugarlabs.org
> http://lists.sugarlabs.org/listinfo/soas

James Cameron

More information about the Sugar-devel mailing list