From owner-freebsd-questions@FreeBSD.ORG Sat Dec 27 13:36:08 2014 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 027531C7 for ; Sat, 27 Dec 2014 13:36:08 +0000 (UTC) Received: from mail.xtaz.uk (tao.xtaz.uk [IPv6:2001:8b0:202::10]) (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 B6C5D1CF9 for ; Sat, 27 Dec 2014 13:36:07 +0000 (UTC) Received: by mail.xtaz.uk (Postfix, from userid 1001) id 424D5209AF2A; Sat, 27 Dec 2014 13:36:04 +0000 (GMT) Date: Sat, 27 Dec 2014 13:36:04 +0000 From: Matt Smith To: Andrew Berg Subject: Re: Do I want to switch to the new pkg(8) format? Message-ID: <20141227133604.GA40611@xtaz.uk> Mail-Followup-To: Matt Smith , Andrew Berg , freebsd-questions@freebsd.org References: <549E06EA.20008@my.hennepintech.edu> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Disposition: inline In-Reply-To: <549E06EA.20008@my.hennepintech.edu> User-Agent: Mutt/1.5.23 (2014-03-12) Cc: freebsd-questions@freebsd.org X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 27 Dec 2014 13:36:08 -0000 On Dec 26 19:10, Andrew Berg wrote: >On 2014.12.26 18:48, Warren Block wrote: >> Actually, pkg_cutleaves is a port and should be okay to use. The name >> is due to it trying to look like the old pkg_* system programs. >> Probably we should say "do not use /usr/sbin/pkg_*". >Unless it has been updated recently, pkg_cutleaves doesn't support pkgng. It >does some weird things that make it look like it kind of works, but it doesn't. >pkg-rmleaf, however, does work with pkgng. Hmmmm. I've been using pkg_cutleaves with pkgng for what must be coming up to a year and haven't ever seen it do anything strange. Seems to work fine to me. It definitely picks appropriate ports to delete and actually uninstalls them using the proper pkgng tools. Can you elaborate a bit on the weird things? Strangely I've just looked at the commit logs for the port to see if there are any clues as to when it was updated to use pkgng and there are none that are obvious. -- Matt