Supercollider in wheezy

[Felipe Sateler]

Dear Relase Team,

I write to fix the issue of supercollider in wheezy. Current SC in
testing is upstream version 3.4.5. Current in sid is 3.5.3. The
version in wheezy has a FTBFS bug (#674386), so we need to get rid of
that. Options are:

1. Upload a fix via tpu.
2. Migrate 3.5.3 to wheezy (we had uploaded 3.5.2 before the freeze,
but it didn't migrate because it didn't build in some archs. More
details later).
3. Remove sc from wheezy.

We would like to avoid option 3, and we favor option 2.  At [1] there
is a description of the changes since the uploaded 3.5.2 version
before the freeze and the current version in unstable.

We would prefer the 3.5 series over the 3.4 series for the following reasons:

* SC 3.4.x relied optionally on a third-party java-based kit
("SwingOSC") to provide for building user interface widgets. (This
provides standard server- and addon-management interfaces as well as
user-made GUIs. It's not compulsory to have GUIs but it's typically
assumed in tutorials and the official book.) This was never packaged
for debian, so the provision is kinda incomplete. SC 3.5 includes a
QT-based widget system which provides all of this functionality and
with the same programming interface. It's very nice.

* The GEdit plugin "sced" has been updated to support GEdit version 3,
which is what is in wheezy. (We previously just deactivated the gedit
plugin in wheezy which is a shame as it's a recommended editor for
beginners.)

* The old and overgrown SCons build system has been removed in favour
of Cmake. Requires much less downstream packaging effort.

* User config files are moved to a much more XDG-friendly location:
instead of ~/share/supercollider   it's now
~/.local/share/SuperCollider and ~/.config/SuperCollider.   (Old
config is detected and migration info is output.)

* Other changes, detailed in http://doc.sccode.org/Guides/News-3_5.html


If a migration of sc from sid to testing is unacceptable, we can
upload a fix to t-p-u. However, g++ 4.7 ICEs while building 3.4.
Therefore, the fix would have to include a build-dependency on gcc/g++
4.6 and force its use in debian/rules, besides the fix for the build
failure. Full diff attached.


[1] http://lists.alioth.debian.org/pipermail/pkg-multimedia-maintainers/2012-July/028351.html

-- 

Saludos,
Felipe Sateler
-------------- next part --------------
A non-text attachment was scrubbed...
Name: wheezy.diff
Type: application/octet-stream
Size: 1494 bytes
Desc: not available
URL: <http://lists.alioth.debian.org/pipermail/pkg-multimedia-maintainers/attachments/20120815/ac679eb9/attachment.obj>