From owner-freebsd-stable@FreeBSD.ORG Sun Jun 3 04:24:42 2012 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 0AD25106566B for ; Sun, 3 Jun 2012 04:24:42 +0000 (UTC) (envelope-from erichfreebsdlist@ovitrap.com) Received: from alogreentechnologies.com (alogreentechnologies.com [67.212.226.44]) by mx1.freebsd.org (Postfix) with ESMTP id B2C098FC18 for ; Sun, 3 Jun 2012 04:24:41 +0000 (UTC) Received: from x220.ovitrap.com ([122.129.201.78]) (authenticated bits=0) by alogreentechnologies.com (8.13.1/8.13.1) with ESMTP id q534Oarw008286; Sat, 2 Jun 2012 22:24:40 -0600 From: Erich To: freebsd-stable@freebsd.org Date: Sun, 03 Jun 2012 11:24:30 +0700 Message-ID: <2683532.ZXZgRCPEVi@x220.ovitrap.com> User-Agent: KMail/4.8.3 (Linux/3.3.7-1.fc16.x86_64; KDE/4.8.3; x86_64; ; ) In-Reply-To: <20120602195022.GG5335@home.opsec.eu> References: <95D35900-AC63-4948-B54F-40041FFCB232@gromit.dlib.vt.edu> <20120602195022.GG5335@home.opsec.eu> MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" Cc: Kurt Jaeger Subject: Re: Why Are You NOT 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: Sun, 03 Jun 2012 04:24:42 -0000 Hi, On 02 June 2012 PM 9:50:22 Kurt Jaeger wrote: > Hi! > > > The point he made was actually not a matter of people not reading > > UPDATING but that UPDATING is oftentimes not updated until after > > the disruptive/potentially dangerous change has already hit the > > ports tree. > > > > I'm not sure what the solution is for the end user. > > We have our reference hosts, do daily portupgrades and on those days > where all looks fine, pkg_create the whole collection and pkg_delete/pkg_add > to production hosts. > > Still not perfect, but 'good enough'. > > isn't this what I just suggested to be done by the team? Give the ports tree a new version number and people can fall back to this then. Isn't this solution too simple to be done? Erich