From owner-freebsd-ports@FreeBSD.ORG Wed Feb 12 02:36:53 2014 Return-Path: Delivered-To: freebsd-ports@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 22D295AF for ; Wed, 12 Feb 2014 02:36:53 +0000 (UTC) Received: from gate.utahime.jp (ipq210.utahime.jp [183.180.29.210]) by mx1.freebsd.org (Postfix) with ESMTP id E154515D1 for ; Wed, 12 Feb 2014 02:36:52 +0000 (UTC) Received: from eastasia.home.utahime.org (eastasia.home.utahime.org [192.168.174.1]) by gate.utahime.jp (Postfix) with ESMTP id B9DCC4E641; Wed, 12 Feb 2014 11:36:44 +0900 (JST) Received: from eastasia.home.utahime.org (localhost [127.0.0.1]) by localhost-backdoor.home.utahime.org (Postfix) with ESMTP id 8292E75942; Wed, 12 Feb 2014 11:36:44 +0900 (JST) Received: from localhost (rolling.home.utahime.org [192.168.174.11]) by eastasia.home.utahime.org (Postfix) with ESMTPA id 2DD797591E; Wed, 12 Feb 2014 11:36:44 +0900 (JST) Date: Wed, 12 Feb 2014 11:35:26 +0900 (JST) Message-Id: <20140212.113526.426297070.yasu@utahime.org> To: freebsd-ports@freebsd.org Subject: Way to list both direct and indirect dependency together with PKGNG From: Yasuhiro KIMURA X-Mailer: Mew version 6.5 on Emacs 24.3 / Mule 6.0 (HANACHIRUSATO) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Virus-Scanned: ClamAV using ClamSMTP X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 12 Feb 2014 02:36:53 -0000 As previously announced, now dependency of package is not registered recursively if PKGNG is used, and both 'pkg info -d' and 'pkg info -r' show only direct dependency. Then are there any easy way (program, script, simple one-liner etc.) to list all (both direct and indirect) dependency with PKGNG? My intention is to check if there are programs to be restarted when some packages are updated. So simple list of packages is enough and no further information such as dependency tree is required. Regards. --- Yasuhiro KIMURA