From owner-freebsd-questions@FreeBSD.ORG  Wed Jan 29 09:03:18 2014
Return-Path: <owner-freebsd-questions@FreeBSD.ORG>
Delivered-To: freebsd-questions@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115])
 (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits))
 (No client certificate requested)
 by hub.freebsd.org (Postfix) with ESMTPS id 098D8D8C
 for <freebsd-questions@freebsd.org>; Wed, 29 Jan 2014 09:03:18 +0000 (UTC)
Received: from smtprelay01.ispgateway.de (smtprelay01.ispgateway.de
 [80.67.29.23])
 (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits))
 (No client certificate requested)
 by mx1.freebsd.org (Postfix) with ESMTPS id B6E58113A
 for <freebsd-questions@freebsd.org>; Wed, 29 Jan 2014 09:03:17 +0000 (UTC)
Received: from [134.95.7.245] (helo=elfsechsundzwanzig.de)
 by smtprelay01.ispgateway.de with esmtpsa (TLSv1:AES256-SHA:256)
 (Exim 4.68) (envelope-from <lists@elfsechsundzwanzig.de>)
 id 1W8R36-0004an-BB; Wed, 29 Jan 2014 10:03:08 +0100
Date: Wed, 29 Jan 2014 10:03:08 +0100
From: _1126 <lists@elfsechsundzwanzig.de>
To: Walter Hurry <walterhurry@gmail.com>
Subject: Re: [freebsd-questions] Re: Re: [freebsd-questions] Re:
 [freebsd-questions] Re: weird error messages with various ports
Message-ID: <20140129090308.GA3535@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>
 <20140128172449.73adf28a@X220.alogt.com>
 <lc8m85$9bp$1@ger.gmane.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable
In-Reply-To: <lc8m85$9bp$1@ger.gmane.org>
User-Agent: Mutt/1.5.22 (2013-10-16)
X-Df-Sender: bGlzdHNAZWxmc2VjaHN1bmR6d2FuemlnLmRl
Cc: freebsd-questions@freebsd.org
X-BeenThere: freebsd-questions@freebsd.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: User questions <freebsd-questions.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-questions>, 
 <mailto:freebsd-questions-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-questions/>
List-Post: <mailto:freebsd-questions@freebsd.org>
List-Help: <mailto:freebsd-questions-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-questions>, 
 <mailto:freebsd-questions-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Wed, 29 Jan 2014 09:03:18 -0000

On Tue, Jan 28, 2014 at 04:35:17PM +0000, Walter Hurry wrote:
> Erich Dollansky wrote:
>=20
> > Hi,
> >
> > On Tue, 28 Jan 2014 09:49:35 +0100
> > _1126 <lists@elfsechsundzwanzig.de> wrote:
> >
> >>=20
> >> 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,
>=20
> Your replies in this thread have been illuminating. In the light of
> them, I have decided to stick with portupgrade, but to move ports
> updating from portsnap to svn, for the extra flexibility.

I think I'll do the same. At least the svn part. Have to figure out
how to deal with custom configured ports, though. In the worst case,
I'll reconfigure and rebuild all ports.=20


=20
> Thanks!

Thanks indeed.