Date: Sat, 27 Dec 2014 13:36:04 +0000 From: Matt Smith <fbsd@xtaz.co.uk> To: Andrew Berg <aberg010@my.hennepintech.edu> Cc: freebsd-questions@freebsd.org Subject: Re: Do I want to switch to the new pkg(8) format? Message-ID: <20141227133604.GA40611@xtaz.uk> In-Reply-To: <549E06EA.20008@my.hennepintech.edu> References: <CAPi0psuei36LjMFT_B7DF3dWhTz=RK28r-kxKdyeNJx1YSapdg@mail.gmail.com> <CAPi0psv8V7=VZUJS4ND-d=gx4Rh16q8p3p-y2Naac0WCRzcT2w@mail.gmail.com> <alpine.BSF.2.11.1412261740280.26354@wonkity.com> <549E06EA.20008@my.hennepintech.edu>
next in thread | previous in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20141227133604.GA40611>