Re: reasons for split of libavcodec54 and libavcodec-extra-54, missing codecs and a metapackage.

2014-11-22 Thread Reinhard Tartler
On Sat, Nov 22, 2014 at 6:51 AM, Andreas Cadhalpun wrote: > Hi, > > On 22.11.2014 10:11, Fabian Greffrath wrote: >> >> I have two more ideas regarding this issue: >> >> 1) We have two library packages that conflict with each other. Why don't >> we have two -dev packages that conflict with each oth

Re: reasons for split of libavcodec54 and libavcodec-extra-54, missing codecs and a metapackage.

2014-11-22 Thread Reinhard Tartler
On Sat, Nov 22, 2014 at 4:11 AM, Fabian Greffrath wrote: > I have two more ideas regarding this issue: > > 1) We have two library packages that conflict with each other. Why don't > we have two -dev packages that conflict with each other, then? > > I suggest to introduce a new libavcodec-extra-dev

Re: reasons for split of libavcodec54 and libavcodec-extra-54, missing codecs and a metapackage.

2014-11-22 Thread Reinhard Tartler
On Thu, Nov 20, 2014 at 9:02 PM, Jonas Smedegaard wrote: > Hi Reinhard, > > Quoting Reinhard Tartler (2014-11-20 21:45:56) >> On Nov 20, 2014 3:01 PM, "Jonas Smedegaard" <[1]d...@jones.dk> wrote: >>> Quoting Andreas Cadhalpun (2014-11-20 17:09:49) On 19.11.2014 13:09, Jonas Smedegaard wrote:

Re: reasons for split of libavcodec54 and libavcodec-extra-54, missing codecs and a metapackage.

2014-11-22 Thread Andreas Cadhalpun
Hi, On 22.11.2014 13:48, Felipe Sateler wrote: On Sat, Nov 22, 2014 at 8:51 AM, Andreas Cadhalpun wrote: That's a nice idea, but just as the shlibs.local method, it doesn't work in all cases. See my previous example of libkfilemetadata4, which would still have the problem, because it only indi

Re: reasons for split of libavcodec54 and libavcodec-extra-54, missing codecs and a metapackage.

2014-11-22 Thread Felipe Sateler
On Sat, Nov 22, 2014 at 8:51 AM, Andreas Cadhalpun wrote: > Hi, > > On 22.11.2014 10:11, Fabian Greffrath wrote: >> >> I have two more ideas regarding this issue: >> >> 1) We have two library packages that conflict with each other. Why don't >> we have two -dev packages that conflict with each oth

Re: reasons for split of libavcodec54 and libavcodec-extra-54, missing codecs and a metapackage.

2014-11-22 Thread Andreas Cadhalpun
Hi, On 22.11.2014 10:11, Fabian Greffrath wrote: I have two more ideas regarding this issue: 1) We have two library packages that conflict with each other. Why don't we have two -dev packages that conflict with each other, then? I suggest to introduce a new libavcodec-extra-dev package that de

Re: reasons for split of libavcodec54 and libavcodec-extra-54, missing codecs and a metapackage.

2014-11-22 Thread Jonas Smedegaard
Quoting Fabian Greffrath (2014-11-22 10:11:43) > I have two more ideas regarding this issue: > > 1) We have two library packages that conflict with each other. Why don't > we have two -dev packages that conflict with each other, then? > > I suggest to introduce a new libavcodec-extra-dev package

Re: reasons for split of libavcodec54 and libavcodec-extra-54, missing codecs and a metapackage.

2014-11-22 Thread Fabian Greffrath
I have two more ideas regarding this issue: 1) We have two library packages that conflict with each other. Why don't we have two -dev packages that conflict with each other, then? I suggest to introduce a new libavcodec-extra-dev package that depends on "libavcodec | libavcodec-extra" and change