From owner-freebsd-questions@FreeBSD.ORG Wed Jun 11 13:21:28 2003 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 731E837B401 for ; Wed, 11 Jun 2003 13:21:28 -0700 (PDT) Received: from pa-plum1b-166.pit.adelphia.net (pa-plum1b-217.pit.adelphia.net [24.53.161.217]) by mx1.FreeBSD.org (Postfix) with ESMTP id AC92B43F75 for ; Wed, 11 Jun 2003 13:21:27 -0700 (PDT) (envelope-from wmoran@potentialtech.com) Received: from potentialtech.com (working [172.16.0.95]) h5BKLAOg001693; Wed, 11 Jun 2003 16:21:16 -0400 (EDT) (envelope-from wmoran@potentialtech.com) Message-ID: <3EE78F36.5090409@potentialtech.com> Date: Wed, 11 Jun 2003 16:21:10 -0400 From: Bill Moran User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.3) Gecko/20030429 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Mark Miller References: <20030611130828.E25932-100000@soda.csua.berkeley.edu> In-Reply-To: <20030611130828.E25932-100000@soda.csua.berkeley.edu> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit cc: freebsd-questions@freebsd.org Subject: Re: Are there STABLE/CURRENT/RELEASE tags for 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: Wed, 11 Jun 2003 20:21:28 -0000 Mark Miller wrote: > Hi, > > Are there any equivalents to STABLE/RELEASE/CURRENT for ports? I've been > cvsup'ing with "tag=." for awhile and I keep getting build errors (bug > reports will be filed soon). Is there a way to just track -STABLE ports > (maybe that only have bugfixes and security updates) that are more likely > to play nicely with each other? If not, is there any way to make this > happen? There are no STABLE, etc tags like you describe for ports. All ports should build properly, unless marked broken for forbidden. When that is the case, you don't get build errors, you get a message like: "SuperSoftware is broken on FreeBSD 5 because it won't build with this version of GCC" If you're getting lots of build errors, I would suspect that something is either wrong with your ports tree or with your FreeBSD installation. Step 1: rm -r /usr/ports/* Step 2: recvsup your ports Step 3: Try again Step 4: If 3 doesn't work, ask here about the specific failure that you have occurring. Step 5: If you still don't get it working, and people on this list claim that it works for them, then you'll need to reinstall FreeBSD I may get flamed for #5, but it's the only way I've fixed build failures on occasion. I just had this happen today (see earlier thread on Apache+modssl) and cvsup/buildworld/installworld, reinstalling all ports, recvsupping the ports tree ... none of it worked. Then I wiped the drive and installed FreeBSD from scratch and everything built like magic. This was on a test machine that frequently gets used for all sorts of experimenting, so I can only assume that someone did something very bad to it (even though it operated without incident in every manner except building ports). -- Bill Moran Potential Technologies http://www.potentialtech.com