Date: Sat, 5 Apr 2014 15:15:31 +0300 From: "Reko Turja" <reko.turja@liukuma.net> To: <freebsd-ports@freebsd.org> Cc: Robert Huff <roberthuff@rcn.com> Subject: Re: pkgng abilities (was: pkgng vs. portupgrade reporting ports outdated) Message-ID: <D2CE17BC2ED04C5094732D71D39287E1@Rivendell> In-Reply-To: <533FEF44.10302@rcn.com> References: <533FEF44.10302@rcn.com>
next in thread | previous in thread | raw e-mail | index | archive | help
-----Original Message----- From: Robert Huff > OK, Obi-wan - what's the replacement for: > a) "portsclean" with the C, D (single and double), and L > options? (Use no more than two commands.) > b) "pkg_sort" ? > > With these, I will cheerfully delete portupgrade. portupgrade != pkg_old Actually, for me portupgrade with pkgng is getting close the ideal solution, made yesterday the portsnap fetch upgrade portversion -v | grep -v '=' portupgrade -rf php5 dance and got the whole php rebuild from source with one minor hitch. Due the way extensions.ini is "rebuilt" every php installation I got wrong module order and couple of modules got signal 11's when trying to rebuild. After manually correcting extensions.ini order I just portupgrade -f'd the 2 failed packages in dependency order, this time without any problems. pkgng pretty nicely built just the stuff that needed rebuild, not half the installed ports. I'm already running php in cgi mode, so no mod for apache was needed (and due the recent improvement, the said mod was not autoinstalled to my httpd.conf either). -Reko
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?D2CE17BC2ED04C5094732D71D39287E1>