From owner-freebsd-ports@FreeBSD.ORG Tue Aug 4 07:21:02 2009 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id DC5D3106566C; Tue, 4 Aug 2009 07:21:02 +0000 (UTC) (envelope-from perryh@pluto.rain.com) Received: from agora.rdrop.com (unknown [IPv6:2607:f678:1010::34]) by mx1.freebsd.org (Postfix) with ESMTP id B56728FC19; Tue, 4 Aug 2009 07:21:02 +0000 (UTC) (envelope-from perryh@pluto.rain.com) Received: from agora.rdrop.com (66@localhost [127.0.0.1]) by agora.rdrop.com (8.13.1/8.12.7) with ESMTP id n747L2KG081670 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Tue, 4 Aug 2009 00:21:02 -0700 (PDT) (envelope-from perryh@pluto.rain.com) Received: (from uucp@localhost) by agora.rdrop.com (8.13.1/8.12.9/Submit) with UUCP id n747L2tr081669; Tue, 4 Aug 2009 00:21:02 -0700 (PDT) Received: from fbsd61 by pluto.rain.com (4.1/SMI-4.1-pluto-M2060407) id AA02613; Tue, 4 Aug 09 00:12:01 PDT Date: Tue, 04 Aug 2009 00:08:47 -0700 From: perryh@pluto.rain.com To: cperciva@freebsd.org Message-Id: <4a77de7f.wcA106S2uM5ht3Xq%perryh@pluto.rain.com> References: <9EC698AF-15E1-4B95-A7BB-B0E4B7063B25@optusnet.com.au> <200908031409.46060.mel.flynn+fbsd.ports@mailing.thruhere.net> <4A776512.9020509@freebsd.org> In-Reply-To: <4A776512.9020509@freebsd.org> User-Agent: nail 11.25 7/29/05 Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Cc: freebsd-ports@freebsd.org Subject: Re: freebsd-update & userland sources X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 04 Aug 2009 07:21:03 -0000 Colin Percival wrote: > > On Sunday 02 August 2009 16:10:37 Tom Mende wrote: > >> Is there a way to get freebsd-update to keep userland sources > >> up to date? > Yes. If you have source code installed (for the right version of > FreeBSD) in /usr/src, then freebsd-update will keep it updated. > > (Slight complication: Because freebsd-update builds are normally > done before patches are committed to SVN, you won't get the > updated SVN revision numbers ... For someone using the source primarily for reference or to build the occasional port that needs it -- the OP's case, and likely typical of binary-update users -- this seems harmless enough. > ... or the new entries in UPDATING ... This seems not so good. The archives are overflowing with problems arising from failure to read UPDATING :( I'd think it desirable to find a way to keep it current. > ... via freebsd-update -- but you will get all of the > security/errata fixes.)