From owner-freebsd-questions@FreeBSD.ORG Wed Sep 10 17:48:23 2008 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 333241065673 for ; Wed, 10 Sep 2008 17:48:23 +0000 (UTC) (envelope-from relay.lists@gmail.com) Received: from mail-gx0-f17.google.com (mail-gx0-f17.google.com [209.85.217.17]) by mx1.freebsd.org (Postfix) with ESMTP id CB4DF8FC1B for ; Wed, 10 Sep 2008 17:48:22 +0000 (UTC) (envelope-from relay.lists@gmail.com) Received: by gxk10 with SMTP id 10so14266982gxk.19 for ; Wed, 10 Sep 2008 10:48:22 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to :subject:in-reply-to:mime-version:content-type :content-transfer-encoding:content-disposition:references; bh=qRWG37xa7URPgh2rLtUP4CQLT/UmooSr77jUwhbMx5o=; b=K5lwsqD6MimWj6wmqnTxf7xnBY94/qm9S+tkN4zmlO5I/S1w5EzCmng7sG7/B5fCyf DGBA+Br6R9xwxuoex7B4/QQz/Q9jRlv+Tzyg9Jy17TzT5nEDcoX7HXGGq0v94sLJgq+z RuXSHqqYrnwLudmQK+CxNmmK794QPOyAkdlvo= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:in-reply-to:mime-version :content-type:content-transfer-encoding:content-disposition :references; b=qEMFtGSu/i5hMcFSX0yeMgA5A7OID+HnpkLlauIo6xWyfTWp+q6Of2PSkwJWCVOeit 0XX9Rpav/CUVFkqfOzMOtMxEmK7LbyhJY02sJW2yZrBsVLQvYjAFEPlf0opGhzS27nOB Smy8U0wixjUJw6V0WiHbhuQIiQQDSyy7QXJKs= Received: by 10.90.93.13 with SMTP id q13mr1788450agb.106.1221068901873; Wed, 10 Sep 2008 10:48:21 -0700 (PDT) Received: by 10.90.88.20 with HTTP; Wed, 10 Sep 2008 10:48:20 -0700 (PDT) Message-ID: Date: Wed, 10 Sep 2008 20:48:20 +0300 From: "Lister Notifies" To: freebsd-questions@freebsd.org In-Reply-To: <48C7EBC1.2030106@za.verizonbusiness.com> MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <20080910162227.0241e209@ilievnet.com> <48C7EBC1.2030106@za.verizonbusiness.com> Subject: Re: branches, updates, buildworld X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 10 Sep 2008 17:48:23 -0000 On 9/10/08, Todor Genov wrote: > > relay.lists@gmail.com wrote: > > Hi, --snip-- > > 1) After reading the docs I remained with the impression that sources > > should be updated for "-current" and "-stable" branches only. Is this > > correct? > > The STABLE and CURRENT branch are works-in-progress and change daily, > thus if you wish to follow them you need to update your sources quite > frequently. > > The only time the RELEASE branch changes (and needs to be updated) is > when security and bug fixes are applied to the current source tree - > these are known as RELEASE-p? versions. You can follow these updates at > http://security.freebsd.org/advisories and on the > freebsd-security-notifications mailing list. > > > > 2) If I'm wrong about (1) how should I update the "-release" sources in > > order to "make buildworld" with additional gcc optimisations? > > > make buildworld in /usr/src will compile whatever sources you have in > the directory. Whether the compiled code is optimized depends on what > you put in /etc/make.conf > > If you haven't done a cvsup since your installation then you have the > 7.0-RELEASE source which was on the CD. > > If you want to obtain the latest 7.0-RELEASE-p? source you need to > cvsup with tag=RELENG_7_0 in the cvsup config file. Thereafter you do a > buildworld/installworld (and buildkernel/installkernel) which will then > give you the latest -RELEASE version (7.0-RELEASE-p4 if I am not mistaken). Thank you! Exactly what I wanted to know. > Similarly tag=RELENG_7 will fetch the -STABLE branch and tag=. will > fetch the -CURRENT branch, but you should probably stick with RELENG_7_0 Nope, it's too soon for me to deal with moving targets. So, I guess I need the rock-stable version until I get familiar with the OS. > > > > 3) "make buildworld" re-compiles _everything_ or the "base system" only? > > > It recompiles the base system. For updates to packages installed from > ports look at portupgrade. OK. It brings another question. For example Postgres is not a part of the base system. Will it break if i make: ## pkg_add -r postgresql83-server.tbz cvsup /usr/share/examples/cvsup/standard-supfile make buildworld make buildkernel make installkernel reboot (in single mode) mergemaster -p make installworld mergemaster reboot ## ...And what should I do if Postgres (or any other arbitrary binary package) breaks afterwards? How should I keep the binary packages up-todate? Actually I intend to compile Postgres from the ports after success in re-building and installing the base system, but the question still remains. > > > > 4) Will "make buildworld" fail with a make.conf like this: > > Seems OK on first inspection. Guess you won't know till you run the > buildworld :) I was kind of hoping not to figure out the optimal combination of gcc flags by following the "generate and test" method on Pentium-2. :) Last but not least: Thanks for the fast and detailed response. I appreciate it very much.