From mboxrd@z Thu Jan 1 00:00:00 1970 From: taylanbayirli@gmail.com (Taylan Ulrich =?utf-8?Q?Bay=C4=B1rl=C4=B1?= =?utf-8?Q?=2FKammer?=) Subject: Re: pkg-config "Requires" fields and propagated inputs Date: Wed, 25 Mar 2015 20:48:20 +0100 Message-ID: <87d23w270b.fsf@taylan.uni.cx> References: <87d2444stf.fsf@taylan.uni.cx> <87twxayuz6.fsf@gnu.org> <877fu62el9.fsf@taylan.uni.cx> <87y4mlrp7e.fsf@gnu.org> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:35621) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1YarHt-0003Vg-04 for guix-devel@gnu.org; Wed, 25 Mar 2015 15:48:25 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1YarHs-0007rD-4O for guix-devel@gnu.org; Wed, 25 Mar 2015 15:48:24 -0400 In-Reply-To: <87y4mlrp7e.fsf@gnu.org> ("Ludovic \=\?utf-8\?Q\?Court\=C3\=A8s\=22'\?\= \=\?utf-8\?Q\?s\?\= message of "Wed, 25 Mar 2015 17:56:05 +0100") List-Id: "Development of GNU Guix and the GNU System distribution." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: guix-devel-bounces+gcggd-guix-devel=m.gmane.org@gnu.org Sender: guix-devel-bounces+gcggd-guix-devel=m.gmane.org@gnu.org To: Ludovic =?utf-8?Q?Court=C3=A8s?= Cc: guix-devel@gnu.org ludo@gnu.org (Ludovic Court=C3=A8s) writes: > taylanbayirli@gmail.com (Taylan Ulrich "Bay=C4=B1rl=C4=B1/Kammer") skribi= s: > >> It might be nice to have build-only propagated inputs. On the other >> hand, someone installing libxrandr in their profile will expect >> pkg-config on libxrandr to work without errors. More generally, they >> will expect any build operation to work; i.e. a user might want to use >> Guix-installed libraries for Guix-external development, and build-only >> propagated inputs would mean annoying such users because they now have >> to install them manually. Unless we provide a special "install for >> development" operation that is. But the complexity grows. :-) > > Heh. Another option would be to have per-output propagated inputs. > That is, if a package has =E2=80=9Cout=E2=80=9D and =E2=80=9Clib=E2=80=9D= outputs, you=E2=80=99d want the > propagated inputs to apply only to =E2=80=9Clib=E2=80=9D since this is wh= ere the .pc is. > (This has been in =E2=80=98TODO=E2=80=99 for a couple of years.) > > Thoughts? Sounds like an obvious feature to add, and in my (limited) experience these library deps are the most common propagated inputs... Taylan