Date: Thu, 10 Jan 2013 17:24:27 -0700 (MST) From: Warren Block <wblock@wonkity.com> To: Jeffrey Bouquet <jeffreybouquet@yahoo.com> Cc: jsa@FreeBSD.org, ports@FreeBSD.org, freebsd-ports@freebsd.org Subject: Re: FreeBSD Port: portmanager-0.4.1_9 Message-ID: <alpine.BSF.2.00.1301101721310.11401@wonkity.com> In-Reply-To: <1357860854.69357.YahooMailClassic@web164003.mail.gq1.yahoo.com> References: <1357860854.69357.YahooMailClassic@web164003.mail.gq1.yahoo.com>
next in thread | previous in thread | raw e-mail | index | archive | help
This message is in MIME format. The first part should be readable text, while the remaining parts are likely unreadable without MIME-aware tools. --3512871622-3001972-1357863867=:11401 Content-Type: TEXT/PLAIN; charset=iso-8859-1; format=flowed Content-Transfer-Encoding: 8BIT On Thu, 10 Jan 2013, Jeffrey Bouquet wrote: > BTW portmanager was excellent the for the first few years. One could begin an update, then cntl-c after a few minutes when it actually began building ports, and up in the terminal would be a concise list of what needed to be installed or upgraded. Later, its results were inaccurate (did not find installed ports...). It would serve many well if someone were to rewrite if for the present ports structure IMHO. (That was for just one of its usages that I used a lot, the others I was still using portupgrade or a custom .sh script, for those fifty percent or so > of the time in which I did not simply permit portmanager to complete the task.) portupgrade -na does that also. That and portupgrade's -R function (rebuild everything that the named port depends on, and then the named port) are the only thing I miss in portmaster. --3512871622-3001972-1357863867=:11401--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?alpine.BSF.2.00.1301101721310.11401>