kiax in Debian (was Re: Problems rebuilding twinkle)

[George Danchev]

On Saturday 06 May 2006 21:44, Santiago Garcia Mantinan wrote:
> > We pretty much just need to remove the iLBC and update debian/copyright.
> >
> > For extra marks we could link to the system provided libspeex/ libgsm &
> > portaudio..
>
> It seems that is already done:
>
> Version: 0.8.5-2
> Depends: libc6 (>= 2.3.6-6), libgcc1 (>= 1:4.1.0), libgsm1 (>= 1.0.10),
> libportaudio0, libqt3-mt (>= 3:3.3.6), libspeex1, libstdc++6 (>= 4.1.0),
> libx11-6, libxext6
>
> > George Danchev was talking to upstream to get something along those lines
> > in the next upstream release, but I haven't followed anything since.
>
> Well, George, how did that go? For what I see the new version still carries
> all the stuff we didn't want, including iLBC, so I suppose we should at
> least remove iLBC from our source package.

Upstream said that they distributing the stuff in kiax's lib/ because these 
libraries are not stable enough (sort of true, but we have sonames to handle 
these out) in addition that we can live without lib/ anyway. I sent them a 
patch (ca. November 05) against 0.8.4 to clean the iLBC stuff up. You can 
have it at:

svn co http://svn.openfmi.net/dev/people/danchev/kiax

which was not incorporated in 0.8.5 - reasons unknown for the time being.

> I have tested it and we can remove the hole lib directory and the program
> still compiles, so I guess we could have a source package without this
> directory and that would make half of our problems go away, isn't it?
>
> What I don't know is what we'd loose by removing this directory, iLBC for
> sure, but that was a wanted effect anyway. But there were some dirs there
> like sox, portmixer, ... that we don't have as a shared lib, so... what
> where those for?

lib/portaudio/LICENSE.txt and 
lib/portmixer/LICENSE.txt sound terribly non-free: 

 * Any person wishing to distribute modifications to the Software is
 * requested to send the modifications to the original developer so that
 * they can be incorporated into the canonical version.

Thus no anonymous modifications are allowed (a-la send me a postcard 
games ;-), so render these bits as DFSG-compliant.

> As for removing iLBC the source is not ready for that and still shows the
> iLBC button and it is enabled, so if you choose it and make a call you get
> in the console:
>
> ERROR: Codec not supported: 1024
> ERROR: Codec could not be created: 1024
>
> I'll have to investigate this more, but this poses problems when loading a
> config (iLBC should be changed to some other codec like gsm) and then in
> the preferences window where we should either make iLBC not appear or at
> least make it appear disabled.
>
> Thoughts on all this?

My impression is that linking against libgsm we already have in Debian should 
be enough. I'm still not sure how to approach upstream that distributing 
(possibly) modified non-free code with their lib/ is pretty dangerous 
solution for them.

P.S. upstream is CC'ed.

-- 
pub 4096R/0E4BD0AB 2003-03-18 <people.fccf.net/danchev/key pgp.mit.edu>
fingerprint 1AE7 7C66 0A26 5BFF DF22 5D55 1C57 0C89 0E4B D0AB