From mboxrd@z Thu Jan 1 00:00:00 1970 From: ludo@gnu.org (Ludovic =?UTF-8?Q?Court=C3=A8s?=) Subject: bug#30130: Add =?UTF-8?Q?=E2=80=98guix_?= =?UTF-8?Q?whereis=E2=80=99?= command Date: Wed, 17 Jan 2018 15:05:42 +0100 Message-ID: <877esg60nd.fsf@gnu.org> References: <871sirf3fo.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]:36064) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1eboLv-0006Bn-7W for bug-guix@gnu.org; Wed, 17 Jan 2018 09:06:08 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1eboLq-0000hc-6Z for bug-guix@gnu.org; Wed, 17 Jan 2018 09:06:07 -0500 Received: from debbugs.gnu.org ([208.118.235.43]:51669) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1eboLq-0000hL-3R for bug-guix@gnu.org; Wed, 17 Jan 2018 09:06:02 -0500 Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1eboLp-0001uP-My for bug-guix@gnu.org; Wed, 17 Jan 2018 09:06:01 -0500 Sender: "Debbugs-submit" Resent-Message-ID: In-Reply-To: <871sirf3fo.fsf@gnu.org> (Mathieu Lirzin's message of "Mon, 15 Jan 2018 18:16:11 +0100") List-Id: Bug reports for GNU Guix List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: bug-guix-bounces+gcggb-bug-guix=m.gmane.org@gnu.org Sender: "bug-Guix" To: Mathieu Lirzin Cc: 30130@debbugs.gnu.org Mathieu Lirzin skribis: > I would find really useful if Guix was providing a tool similar to what > =E2=80=98dnf whatprovides=E2=80=99 or =E2=80=98apt-file=E2=80=99 does. I= mean something to check what > packages provides a particular file (executable/manual/library). This has been discussed before, and can be summarized this way: 1. Finding files that are already in your store could be done easily, using =E2=80=98updatedb=E2=80=99 or something similar. 2. Finding files from packages not in your store is trickier: it involves getting info from a build farm server typically. If we address #1 in a Guix-specific way (automatically populating a file database upon build completion), then perhaps we could arrange for =E2=80= =98guix publish=E2=80=99 to publish that info. Ludo=E2=80=99.