Date: Tue, 28 Jan 2014 16:35:17 +0000 (UTC) From: Walter Hurry <walterhurry@gmail.com> To: freebsd-questions@freebsd.org Subject: Re: Re: [freebsd-questions] Re: [freebsd-questions] Re: weird error messages with various ports Message-ID: <lc8m85$9bp$1@ger.gmane.org> 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>
next in thread | previous in thread | raw e-mail | index | archive | help
Erich Dollansky wrote: > Hi, > > On Tue, 28 Jan 2014 09:49:35 +0100 > _1126 <lists@elfsechsundzwanzig.de> 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, 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. Thanks!
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?lc8m85$9bp$1>