From owner-freebsd-questions@FreeBSD.ORG Mon Feb 16 13:04:53 2004 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 7665516A4CE for ; Mon, 16 Feb 2004 13:04:53 -0800 (PST) Received: from smtp.owt.com (smtp.owt.com [204.118.6.19]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1E56343D1D for ; Mon, 16 Feb 2004 13:04:53 -0800 (PST) (envelope-from kstewart@owt.com) Received: from localhost.invalid (owt-207-41-94-233.owt.com [207.41.94.233]) by smtp.owt.com (8.12.8/8.12.8) with ESMTP id i1GL499U008806; Mon, 16 Feb 2004 13:04:09 -0800 From: Kent Stewart To: Marty Landman Date: Mon, 16 Feb 2004 13:04:26 -0800 User-Agent: KMail/1.6 References: <6.0.0.22.0.20040216140652.08b2a4d0@pop.face2interface.com> <200402161205.38703.kstewart@owt.com> <6.0.0.22.0.20040216153124.07a309f8@pop.face2interface.com> In-Reply-To: <6.0.0.22.0.20040216153124.07a309f8@pop.face2interface.com> MIME-Version: 1.0 Content-Disposition: inline Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <200402161304.26971.kstewart@owt.com> cc: freebsd-questions@freebsd.org Subject: Re: newbie problem building fetchmail from ports X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 16 Feb 2004 21:04:53 -0000 On Monday 16 February 2004 12:39 pm, Marty Landman wrote: > At 03:05 PM 2/16/2004, Kent Stewart wrote: > >The interface to the gettext library has changed and you have to > > update everything that uses it. You may not be able to do it > > without upgrading to one of the current system releases. I would > > think that it is obvious that you haven't updated your port tree > > for some time. > > I just reinstalled with a 4.8 mini-iso that I d/l'd back in the > summer iirc. Maybe this helps explain some of the issues I've been > plagued with (not including a touch of dandruff, which is more likely > due to the cold weather here). You could try the pkg_add -r feature which will fetch the proper version for your current system. > > This is really just a learning experience for me right now, though > use of the word 'just' seems really lame. Point is that it may be > wise for me to d/l the latest release level mini-iso and reinstall > from that. Eventually I may even learn what I'm doing, though I tend > to doubt it. > hehehe - my way of looking at things is that anyone can be an expert at something on a computer. In addition, no matter how good you get, you will still have embarassing holes that will be pointed out to you in a public forum :). You are getting there when you can do something really dumb and laugh at what you did :). Well, if you are going to learn about cvsup, you might as well learn about making your system current at the same time. The current safe tag for cvsup is RELENG_4_9. I follow RELENG_4, which is stable. There are examples you can use once you install cvsup. I happen to like cvsup-without-gui-16.1h, which is 1 of 2 ports that I suggest should be installed as a port. Going from 4.8 to 4.9 with the security patches is not a big deal. If you screw things up, you can always install from the iso. The suggested way of updating is in /usr/src/UPDATING and a chapter in the handbook is also devoted to the subjec. I typically don't talk about the mini-iso. The iso comes with most of the ports you might be interested in as packages. They are out of date as soon as you install them but you have a working system almost immediately. If you cvsup ports-all, build the indexs, and use portupgrade to move to a current port environment, you have a lot more work ahead of you. Getting current on the ports is something I think you should do but one step at a time is a good idea :). Maintaining your system isn't a big deal, you just have to be able to be consistant. Kent -- Kent Stewart Richland, WA http://users.owt.com/kstewart/index.html