[Sugar-devel] Current status of GTK+ 3.x migration
tony_anderson at usa.net
Sat Dec 26 09:23:47 EST 2015
True - either that or ditch the activities evidently too badly
maintained to work well with modern Sugar.
Aye, There's the rub!
Is the problem 'bad maintenance or none at all' or 'modern' Sugar.
Certainly TuxMath is suffering from 'abandonment'. However, even
abandoned code continues to run when the underlying support is there. In
this case, programmers who were not involved in the development or
maintenance of the code will
The port of activities to GTK+ 3.x seems to have stalled because of the
higher priority to re-implement activities such as
In the case of gstreamer 0.1, I was able to find how to install the codecs:
#script to enable webm, mp3, mp4, m4a, m4v for gstreamer-0.10
sudo cp libgstmad.so /usr/lib/gstreamer-0.10/
sudo chmod 755 /usr/lib/gstreamer-0.10/libgstmad.so
sudo cp libmad.so.0 /usr/lib
sudo chmod 755 /usr/lib/libmad.so.0
sudo cp libgstfaad.so /usr/lib/gstreamer-0.10
sudo chmod 755 /usr/lib/gstreamer-0.10/libgstfaad.so
sudo cp libfaad.so.2.0.0 /usr/lib
sudo chmod 755 /usr/lib/libfaad.so.2.0.0
sudo yum install gstreamer-ffmpeg-0.10.13-8.fc18.i686.rpm
sudo rm -rf /home/olpc/.gstreamer-0.10/registry.i386.bin
The script is the same for XO-1, XO-1.5, XO-1.75, XO-4 except that the
specific files must match the architecture. I have no idea where
/usr/lib/gstreamer-0.10 went in gstreamer-1.0. As I recall,
gstreamer-1.0 does not provide the registry.i386.bin which is required
to register the codecs. Given the limited capacity of the XO what I do
not want to do is install whole repositories, just the necessary files.
I am certainly sure that everyone is bored to tears on this subject
since I have mentioned it so many times already.
On 12/26/2015 01:31 PM, Jonas Smedegaard wrote:
> Quoting Tony Anderson (2015-12-26 16:29:09)
>> Yet more examples of this broken software problem.
> I would call it examples of _unmaintained_ software.
> I.e. in my opinion for these examples the Sugar environment does the
> right thing of both a) moving to GTK+ 3.x while b) providing legacy
> support for GTK+ 2.x for several years. Issues then emerge with
> activities neglecting to migrate for several years to GTK+ 3.x.
>> I have scripts which provide the 'bad and ugly' codecs for GStreamer
>> 0.10 which work very well.
> Which codecs? GStreamer 1.0 also provides bad and ugly codecs - so an
> obvious first step is to ensure they are installed for your system.
> In the case of the Debian system, installing the package
> sugar-jukebox-activity by default pulls in the bad set but you will need
> to explicitly install the ugly set (because the very reason those are
> shipped separately is that they may cause your system to become less
> If, on a Debian system, you install the metapackage sucrose then both
> the bad and ugly sets gets installed (always, not only by default,
> bcause the purpose of that metapackage is to ensure that as much of
> Sucrose as is packaged for Debian gets installed).
>> I have had to regress to Jukebox 26 in order for this to work,
> Sounds like you have done some research on this. I recommend that you
> a) file a bugreport about this (if one is not filed already), and then
> b) refer to the bugreport each time you bring it up - e.g. in
> conversations like this one.
>> Avoiding GTK + 2.x implies porting all 400 Sugar activities to GTK 3!
> True - either that or ditch the activities evidently too badly
> maintained to work well with modern Sugar.
> - Jonas
> Sugar-devel mailing list
> Sugar-devel at lists.sugarlabs.org
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Sugar-devel