Re: what is the difference between a source package and a package (want alsa-lib in stretch)
-----BEGIN PGP SIGNED MESSAGE-----
On Sat, Jan 06, 2018 at 01:38:06PM -0800, Dan Hitt wrote:
> I'm trying to build some software, and one of the long list of items
> to install prior to configuring is 'alsa-lib'.
> I tried
> 'sudo apt-get install alsa-lib'
> but got the message
> 'E: Unable to locate package alsa-lib'
There's no binary package 'alsa-lib'. Often, several binary packages
are built from one source package, each one can then be installed
> So i looked around on the internet, and saw a page for an alsa-lib
> package on debian stretch:
In your case, the page you mention lists all binary packages built
from alsa-lib (libasound, libasound-data, and a couple of others).
Typically, at least one -dev (e.g. for libraries, containing the
headers, when you want to build against the libs), and -doc are
built as separate binary packages: in systems with restricted
storage page, you don't always want the full documentation, for
example. The -udeb  there is, for example, a stripped down
version meant for the installer (in the installer you want just
naked functionality, to keep things small).
If you run the build scripts from the source package, it'll
generate all the binary packages.
- -- t
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (GNU/Linux)
-----END PGP SIGNATURE-----