[CC'ing pkg-multimedia-maintainers as the current toolame maintainers,
pkg-mythtv-maintainers as the current twolame maintainers and
debian-devel for general discussion
I am going to request the removal of the toolame package from unstable
and testing in the short term. toolame hasn't seen a release in six
years, it is dead upstream, it has bugs and is superseded by its
successor twolame (yes, there's a t_o_olame and a t_w_olame). People
should really be using twolame instead, as it has an active upstream,
has its bugs fixed and provides a shared library that is already used
by projects such as gstreamer and audacity.
However, I think the toolame package in stable may stay both for the
convenience of our users and because it's not *that* bad after all. I
have prepared a package targeted at Lenny that fixes two portability
bugs and some minor lintian warnings. It can be found at mentors.d.n
, the debdiff is attached to this mail. Please tell me if or under
which restrictions it is OK to upload it to stable or s-p-u.
My general question regarding the removal of toolame is: Should we
provide a transition and if yes... how? I consider the following
methods to deal with this issue:
1. Remove the toolame package from unstable and testing. End of story.
2. Provide an empty toolame package that depends on twolame.
3a. Provide a wrapper in the toolame package that calls the twolame
binary with the same command line options (or some translations
respectively). toolame and twolame are command line compatible except
for some very exotic flags.
3b. The twolame source creates a toolame package that contains the
above mentioned wrapper script.
4. Make the twolame package provide toolame, so that at least the few
recommends on the toolame package can be satisfied.
5. What else can you imagine/recommend...?
Thank you very much for your suggestions.
Dipl.-Phys. Fabian Greffrath
Lehrstuhl für Energieanlagen und Energieprozesstechnik (LEAT)
Universitätsstr. 150, IB 3/134
Telefon: +49 (0)234 / 32-26334
Fax: +49 (0)234 / 32-14227