From owner-freebsd-pkg@FreeBSD.ORG Sat May 31 13:11:01 2014 Return-Path: Delivered-To: freebsd-pkg@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 9C1F024B for ; Sat, 31 May 2014 13:11:01 +0000 (UTC) Received: from blue.qeng-ho.org (blue.qeng-ho.org [217.155.128.241]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 2F68127C8 for ; Sat, 31 May 2014 13:11:00 +0000 (UTC) Received: from fileserver.home.qeng-ho.org (localhost [127.0.0.1]) by fileserver.home.qeng-ho.org (8.14.7/8.14.5) with ESMTP id s4VDAmKQ025421; Sat, 31 May 2014 14:10:50 +0100 (BST) (envelope-from freebsd@qeng-ho.org) Message-ID: <5389D4D8.6060604@qeng-ho.org> Date: Sat, 31 May 2014 14:10:48 +0100 From: Arthur Chance User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:24.0) Gecko/20100101 Thunderbird/24.5.0 MIME-Version: 1.0 To: Victor Sudakov , freebsd-pkg@freebsd.org Subject: Re: Dependency graph? References: <20140531065218.GB169@admin.sibptus.tomsk.ru> <538991E0.5000902@FreeBSD.org> <20140531122127.GA4538@admin.sibptus.tomsk.ru> In-Reply-To: <20140531122127.GA4538@admin.sibptus.tomsk.ru> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-pkg@freebsd.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: Binary package management and package tools discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 31 May 2014 13:11:01 -0000 On 31/05/2014 13:21, Victor Sudakov wrote: > Matthew Seaman wrote: >>> Sometimes you attempt to "pkg install" a simple package and find out >>> that it attempts to install a load of crap (like X libraries) because of >>> some obscure dependency. >>> >>> Is there a tool that would analyze the repository metadata and display >>> a dependency tree for a package? >>> >>> All the necessary dependency information is already in the repository >>> in JSON (?) or sqlite format, perhaps someone has already come up with >>> a script to display that? >> >> Not to my knowledge. Generating output suitable for feeding into dot >> should be pretty easy, just based on processing the output of 'pkg query' > > To my knowledge, 'pkg query' works with the locally installed packages. > Can it really query a remote repository, and if yes, could you please give an > example query? > > When I issue 'pkg query %do some_package_not_installed_locally', it > returns an empty result. pkg rquery