Bug#656848: libav-dev package?

2012-01-25 Thread Reinhard Tartler
On Mi, Jan 25, 2012 at 13:15:31 (CET), Harald Dunkel wrote: > On 01/23/12 07:22, Reinhard Tartler wrote: >> >> I don't think this would be a great idea. As application maintainer, >> you should know the requirements of your package, and knowing the >> libraries it uses is one part of them. >> > >

Bug#656848: libav-dev package?

2012-01-25 Thread Harald Dunkel
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 01/23/12 07:22, Reinhard Tartler wrote: > > I don't think this would be a great idea. As application maintainer, you > should know the requirements of your package, and knowing the libraries it > uses is one part of them. > Not necessarily. If

Bug#656848: libav-dev package?

2012-01-23 Thread Fabian Greffrath
Am 23.01.2012 07:22, schrieb Reinhard Tartler: I don't think this would be a great idea. As application maintainer, you should know the requirements of your package, and knowing the libraries it uses is one part of them. Having already considered that idea some years ago, this is exactly what

Bug#656848: libav-dev package?

2012-01-22 Thread Reinhard Tartler
tag 656848 wontfix stop On Sun, Jan 22, 2012 at 11:00 AM, Harald Dunkel wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > Package: libav > Version: 4:0.8~beta2-3 > Severity: wishlist > > Would you mind to provide a meta package libav-dev requesting > all the other libav development pa

Bug#656848: libav-dev package?

2012-01-22 Thread Harald Dunkel
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Package: libav Version: 4:0.8~beta2-3 Severity: wishlist Would you mind to provide a meta package libav-dev requesting all the other libav development packages in the same version? This could make writing package build dependencies much easier. Many