From owner-freebsd-questions@FreeBSD.ORG Tue Jan 28 09:35:40 2014 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id D3BAB803 for ; Tue, 28 Jan 2014 09:35:40 +0000 (UTC) Received: from mail.bsdbox.co (122-149-22-79.static.dsl.dodo.com.au [122.149.22.79]) (using TLSv1 with cipher ADH-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 8FA6219EC for ; Tue, 28 Jan 2014 09:35:39 +0000 (UTC) Received: from [10.0.0.4] (122-149-22-79.static.dsl.dodo.com.au [122.149.22.79]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by mail.bsdbox.co (Postfix) with ESMTPSA id 263E62388DA for ; Tue, 28 Jan 2014 09:35:36 +0000 (UTC) Message-ID: <52E779E7.8010800@bsdbox.co> Date: Tue, 28 Jan 2014 20:35:35 +1100 From: nano User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.2.0 MIME-Version: 1.0 To: freebsd-questions@freebsd.org Subject: Re: [freebsd-questions] Re: [freebsd-questions] Re: [freebsd-questions] Re: weird error messages with various ports References: <20140127120519.Horde.zk6gGzrJZ8n-kUHavzPiTw1@webmail.df.eu> <20140127191858.78a3fa5d@X220.alogt.com> <20140127114919.GA66024@elfsechsundzwanzig.de> <20140127200326.026e6c35@X220.alogt.com> <20140127121011.GA68344@elfsechsundzwanzig.de> <20140127203002.37fbb036@X220.alogt.com> <20140128084935.GC16541@elfsechsundzwanzig.de> <20140128172449.73adf28a@X220.alogt.com> In-Reply-To: <20140128172449.73adf28a@X220.alogt.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 28 Jan 2014 09:35:40 -0000 On 28/01/2014 8:24 PM, Erich Dollansky wrote: > Hi, > > On Tue, 28 Jan 2014 09:49:35 +0100 > _1126 wrote: > >> >> I can see why a ports tree that is being checked out with svn instead >> of being updated with portsnap might be a wise choice, but I'm not >> quite sure if I understand correctly what the abilities of portupgrade >> are that portmaster lacks? Do you want to elaborate on that? ;) > > portupgrade never left an un-usable machine after an upgrade for me. As > such, I have no reason to look for any other tool. > > Erich > _______________________________________________ > freebsd-questions@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-questions > To unsubscribe, send any mail to "freebsd-questions-unsubscribe@freebsd.org" > It's left my machine unserviceable a couple times too. Portmaster bails out mid-upgrade if it can't build one port, sometimes leaving apps broken if only so many dependencies are upgraded or if Portmaster deletes a package before realizing it can't build the upgrade. At least portupgrade carries on building what can be built and has a couple extra functions that Portmaster lacks, which adds to its appeal. I used to prefer Portmaster for the --packages-build option, which is incompatible with pkgng, so I think I'll move to portupgrade. -- bsdbox.co