Bug#656848: libav-dev package?

[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 I debianize a huge package I have to know
that it needs ffmpeg or libav at build time, but in which
packages the libav development stuff is split into is not
important. The next libav update might provide a different set
of packages, anyway.

Surely the meta package would be something optional. A shortcut
to make writing control files easier, esp. if you have to look
at the libav version number.

> To be more specific, during my last archive rebuilds, the exact build dependencies gave me a clue what part of libav a package is using, which was helpful for classifying libav's reverse dependencies. This wouldn't be possible at all if all application packages started to build-depend on some
> libav-dev package.
> 

I surely don't know the details of your analysis, but since you
can rebuild libav only as a unit I would have assumed that you
had to rebuild all packages that depend upon _any_ libav dev
package.


Regards

Harri
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)

iEYEARECAAYFAk8f8l4ACgkQUTlbRTxpHjfqkgCdGBWUijeqe6T1CaJ1EJMm0/WE
w6gAn18yjS/TZHk5neg7qSNGgu97Iy7y
=Blgc
-----END PGP SIGNATURE-----