From owner-freebsd-questions@FreeBSD.ORG Tue Jan 28 09:24:59 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 9BFBC368 for ; Tue, 28 Jan 2014 09:24:59 +0000 (UTC) Received: from alogt.com (alogt.com [69.36.191.58]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 71D17191E for ; Tue, 28 Jan 2014 09:24:59 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=alogt.com; s=default; h=Content-Transfer-Encoding:Content-Type:MIME-Version:References:In-Reply-To:Message-ID:Subject:Cc:To:From:Date; bh=B7sS+NAnPb8wyLczxCnNO4x1FwxIvWLUnjGAODzVq1g=; b=Sx01eMbKqigy9ZXHj5gtsejxtToD0Sy6xBjM9VDxXlPSPA23OsCA4brCJNSIIdU+gsMmoPRpWW6NTH5RDnWS1GCG3cSR3cG0RZ4YDUCkaacrG5Vbr+8M8c/u1fKo7HiChZupGEIqJuyBz3laRw/dxJHN4fkrzqjh2L5ycATtEXk=; Received: from [182.10.249.147] (port=13108 helo=X220.alogt.com) by sl-508-2.slc.westdc.net with esmtpsa (SSLv3:DHE-RSA-AES128-SHA:128) (Exim 4.82) (envelope-from ) id 1W84uf-001BTD-CP; Tue, 28 Jan 2014 02:24:58 -0700 Date: Tue, 28 Jan 2014 17:24:49 +0800 From: Erich Dollansky To: _1126 Subject: Re: [freebsd-questions] Re: [freebsd-questions] Re: [freebsd-questions] Re: weird error messages with various ports Message-ID: <20140128172449.73adf28a@X220.alogt.com> In-Reply-To: <20140128084935.GC16541@elfsechsundzwanzig.de> 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> X-Mailer: Claws Mail 3.9.3 (GTK+ 2.24.22; amd64-portbld-freebsd10.0) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: Primary Hostname - sl-508-2.slc.westdc.net X-AntiAbuse: Original Domain - freebsd.org X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12] X-AntiAbuse: Sender Address Domain - alogt.com X-Get-Message-Sender-Via: sl-508-2.slc.westdc.net: authenticated_id: erichsfreebsdlist@alogt.com X-Source: X-Source-Args: X-Source-Dir: Cc: freebsd-questions@freebsd.org 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:24:59 -0000 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