Date: Thu, 17 Dec 2009 14:19:01 +0100 From: Miroslav Lachman <000.fbsd@quip.cz> To: Adam McDougall <mcdouga9@egr.msu.edu> Cc: Jimmy Renner <jimbo@renner.se>, freebsd-ports@freebsd.org Subject: Re: portupgrade failure Message-ID: <4B2A2FC5.1090304@quip.cz> In-Reply-To: <20091217122727.GF10902@egr.msu.edu> References: <7314e5020912161917s355d02c9l16c996043c753044@mail.gmail.com> <19241.45040.505925.616766@jerusalem.litteratus.org> <20091217052400.GC32037@lonesome.com> <20091217102102.15241asjv1rqmqzo@kilroy> <20091217122727.GF10902@egr.msu.edu>
next in thread | previous in thread | raw e-mail | index | archive | help
Adam McDougall wrote: [...] > Some of that sounds true to my experience, for a while I've noticed while > installing a new port with portupgrade that it will install the default > dependencies before prompting with the options screen to find out which > ones I want. For example if I do 'portupgrade -N postfix' on a fresh > system, it will first install pcre and THEN prompt me to (de)select pcre > or any of the other optional deps. [...] It was tired by this behavior more than year ago and it was the main reason to me to switch to portmaster. I got system bloated with unwanted dependencies when using portinstall/portupgrade. I never found what causes this in portupgrade. Miroslav Lachman
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4B2A2FC5.1090304>