From owner-freebsd-stable@FreeBSD.ORG Sat Jun 2 21:53:20 2012 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id D92E2106566B; Sat, 2 Jun 2012 21:53:20 +0000 (UTC) (envelope-from utisoft@gmail.com) Received: from mail-bk0-f54.google.com (mail-bk0-f54.google.com [209.85.214.54]) by mx1.freebsd.org (Postfix) with ESMTP id 38A488FC08; Sat, 2 Jun 2012 21:53:20 +0000 (UTC) Received: by bkvi18 with SMTP id i18so3540597bkv.13 for ; Sat, 02 Jun 2012 14:53:19 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type:content-transfer-encoding; bh=wc2DL4yQe6djPLOWJ0DHn8zvXFVfng62FrO74IlK6Xs=; b=aS1xpVdA4iN66RffLi1Dp4GKH7X6P1pSBmexkr2RMxnsHKbK0dbcb7Zfk4CRXApt6Q js8/jVebzojJmjrO1zACTL5KVHmDBZslhHODyQnVnql67Wys6CI8HF2mUFirDQkCa02X 4Gb+lOMgc3VWQuljjZR8s+pV6mw/vbV1KqMrgsldp46gy+yVMTrBm0XOzCju5/9ofs8M d4VJr20TAfviNlZ7gqXL9Bt25YWNihGA3NlzBRKJ7kKJvZ2SUIZL+OxZvGuk/cb8hJIw rxQ3gA45AKSqDR+ZWpkRpRcAJ2AUByUL/tDCDFGfYXktxTtgTXWa7GaWdt+DNPTr6LTQ EUig== Received: by 10.204.152.196 with SMTP id h4mr4145494bkw.131.1338673999049; Sat, 02 Jun 2012 14:53:19 -0700 (PDT) MIME-Version: 1.0 Received: by 10.204.171.138 with HTTP; Sat, 2 Jun 2012 14:52:48 -0700 (PDT) In-Reply-To: <1405746.nVtAo183hi@x220.ovitrap.com> References: <2189681.al9jQ9fsnP@x220.ovitrap.com> <1405746.nVtAo183hi@x220.ovitrap.com> From: Chris Rees Date: Sat, 2 Jun 2012 22:52:48 +0100 Message-ID: To: Erich Dollansky Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Cc: David Chisnall , freebsd-stable@freebsd.org Subject: Re: Why Are You Using FreeBSD? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 02 Jun 2012 21:53:20 -0000 On 2 June 2012 10:42, Erich Dollansky wrot= e: > Hi, > > On 02 June 2012 AM 9:14:28 Chris Rees wrote: >> On Jun 2, 2012 4:04 AM, "Erich Dollansky" >> wrote: >> > >> > But I have to mention one disadvantage. The ports are in no way linked= to >> the releases. This leads to situations in which a small change in a basi= c >> library will result in a complete update of the installed ports. I >> expressed this already many time here. It would be of advantage if the >> ports tree would also have tags like the base system itself. >> > >> >> Unfortunately this is a massive amount of extra work - we only just keep= up >> with updates as it is. > > I do not think so. At least not for the first step as I see it. Just make= snapshots of the ports tree when the release comes out. These snapshots ar= e with the releases anyway. > > What I did was very simple. I got the ports tree that comes with the rele= ase and installed the system back to the release status. Ok, it was some wo= rk for me - maybe not for others - to find this tree. > > A simple link could help here. > > I do not know if this is just an opinion which is too optimistic. > > What I know is that all the security fixes which appeared since the relea= se are not in there. If I have the choice between three days or more of com= piling and known security holes, I will take the security holes, make the c= lient happy and upgrade after the work for the client is finished. > > I would not expect that FreeBSD will provide more than this. Then you already have all you need-- RELEASEs use packages compiled at time of release if you use pkg_add -r, and the ports tree is tagged at release if you wish to get a 'snapshot'. Note that you will not get any official support if you choose to use a tagged tree :) Chris