> In ubuntu, we do not want ANY applications to be built against the
> *unstripped* variants of libavcodec as a saftey guard. If users want to
> do that at home, fine, but we actually cannot do that in ubuntu because
> that introduces just even more confusion as we already have in this bug.
Understood.
However, I'm not sure, that I got this sentence correctly:
> This means: Building against the regular libavcodec-dev package and then
> replacing libavcodec-unstripped-52...
...
English is not my native language... Do you mean "Build against regular libavcodec-dev and then replace this libavcodec-dev by libavcodec-unstripped-52"?. Or, should I replace libavcodec-unstripped-52 by something?
Side note: I'm pretty sure, kradio does not require "unstripped" libav*-dev packages.. However, I can't install "regular" ones as well, if I have "kubuntu-restricted-extras" installed (and I have it, since it's useful for me), because they conflict.
2Reinhard Tartler:
> In ubuntu, we do not want ANY applications to be built against the
> *unstripped* variants of libavcodec as a saftey guard. If users want to
> do that at home, fine, but we actually cannot do that in ubuntu because
> that introduces just even more confusion as we already have in this bug.
Understood.
However, I'm not sure, that I got this sentence correctly: unstripped- 52...
> This means: Building against the regular libavcodec-dev package and then
> replacing libavcodec-
...
English is not my native language... Do you mean "Build against regular libavcodec-dev and then replace this libavcodec-dev by libavcodec- unstripped- 52"?. Or, should I replace libavcodec- unstripped- 52 by something?
Side note: I'm pretty sure, kradio does not require "unstripped" libav*-dev packages.. However, I can't install "regular" ones as well, if I have "kubuntu- restricted- extras" installed (and I have it, since it's useful for me), because they conflict.
That's the problem..