Re: pkg-config: required as dep so often - How and where to report?

To: debian-user@lists.debian.org
Subject: Re: pkg-config: required as dep so often - How and where to report?
From: Greg Wooledge <wooledg@eeg.ccf.org>
Date: Fri, 4 May 2018 09:58:06 -0400
Message-id: <[🔎] 20180504135806.5c57hcewved4cd5e@eeg.ccf.org>
Mail-followup-to: debian-user@lists.debian.org
In-reply-to: <[🔎] F90F8BAE-0A78-4785-95C0-A623718921E9@compuserve.com>
References: <[🔎] F90F8BAE-0A78-4785-95C0-A623718921E9@compuserve.com>

On Fri, May 04, 2018 at 03:48:26PM +0200, Alexander Traud wrote:
> To compile a (quite large) project, I had to install several packages
> (dependencies). The project required the tool pkg-config. However, that
> was not mentioned anywhere. Still the project compiled/built, because
> one of the other dependencies (libsrtp2-dev) installed pkg-config as
> side effect. So, I had pure luck that it succeeded.

libc6-dev depends on pkg-config, and build-essential depends on libc6-dev.

So I don't think it's necessary.  You're allowed to assume build-essential
is installed, I believe.

Reply to:

Follow-Ups:
- Re: pkg-config: required as dep so often - How and where to report?
  - From: Sven Joachim <svenjoac@gmx.de>

References:
- pkg-config: required as dep so often - How and where to report?
  - From: Alexander Traud <pabstraud@compuserve.com>

Prev by Date: Debian 9 t: Update Gstreamer Base plugins package to resolve a Gstreamer bug
Next by Date: Re: pkg-config: required as dep so often - How and where to report?
Previous by thread: pkg-config: required as dep so often - How and where to report?
Next by thread: Re: pkg-config: required as dep so often - How and where to report?
Index(es):
- Date
- Thread