From owner-freebsd-stable@FreeBSD.ORG Sat Jun 2 18:11:43 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 A9E0C106566B for ; Sat, 2 Jun 2012 18:11:43 +0000 (UTC) (envelope-from paul@gromit.dlib.vt.edu) Received: from lennier.cc.vt.edu (lennier.cc.vt.edu [198.82.162.213]) by mx1.freebsd.org (Postfix) with ESMTP id 5B1AC8FC21 for ; Sat, 2 Jun 2012 18:11:43 +0000 (UTC) Received: from zidane.cc.vt.edu (zidane.cc.vt.edu [198.82.163.227]) by lennier.cc.vt.edu (8.13.8/8.13.8) with ESMTP id q52IB7YR021751; Sat, 2 Jun 2012 14:11:07 -0400 Received: from auth3.smtp.vt.edu (EHLO auth3.smtp.vt.edu) ([198.82.161.152]) by zidane.cc.vt.edu (MOS 4.3.3-GA FastPath queued) with ESMTP id TRJ52415; Sat, 02 Jun 2012 14:11:06 -0400 (EDT) Received: from gromit.chumby.lan (c-98-249-9-133.hsd1.va.comcast.net [98.249.9.133]) (authenticated bits=0) by auth3.smtp.vt.edu (8.13.8/8.13.8) with ESMTP id q52IB601031861 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Sat, 2 Jun 2012 14:11:06 -0400 Mime-Version: 1.0 (Apple Message framework v1278) Content-Type: text/plain; charset=iso-8859-1 From: Paul Mather In-Reply-To: Date: Sat, 2 Jun 2012 14:11:06 -0400 Content-Transfer-Encoding: quoted-printable Message-Id: <95D35900-AC63-4948-B54F-40041FFCB232@gromit.dlib.vt.edu> References: <1405746.nVtAo183hi@x220.ovitrap.com> <4FC9FECC.8090703@digsys.bg> <3303845.JjFTmctz7f@x220.ovitrap.com> <4FCA0B5F.5010500@digsys.bg> <4FCA20C5.6010901@zedat.fu-berlin.de> To: Chris Rees X-Mailer: Apple Mail (2.1278) X-Mirapoint-Received-SPF: 198.82.161.152 auth3.smtp.vt.edu paul@gromit.dlib.vt.edu 5 none X-Junkmail-Status: score=10/50, host=zidane.cc.vt.edu X-Junkmail-Signature-Raw: score=unknown, refid=str=0001.0A02020A.4FCA573B.0003,ss=1,re=0.000,fgs=0, ip=98.249.9.133, so=2011-07-25 19:15:43, dmn=2011-05-27 18:58:46, mode=single engine X-Junkmail-IWF: false Cc: FreeBSD Stable , "O. Hartmann" 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: Sat, 02 Jun 2012 18:11:43 -0000 On Jun 2, 2012, at 1:31 PM, Chris Rees wrote: > On Jun 2, 2012 3:19 PM, "O. Hartmann" = wrote: >>=20 >> On 06/02/12 14:47, Daniel Kalchev wrote: >>>=20 >>>=20 >>> On 02.06.12 15:32, Erich wrote: >>>> I know that the ports tree is a moving target. But it stops moving >>>> during the release period. This could be used to give a fall back >>>> solution. >>>>=20 >>>> Or do I see this really too simple? >>>=20 >>> The ports tree is a moving target during release periods still, = although >>> there are efforts to make movements smaller. This is why, after a >>> release it suddenly moves more :) >>>=20 >>> Daniel >>=20 >> Even IF the ports tree IS a moving target, updating of UPDATING, for >> instance, follows most times AFTER the critical ports has been >> changed/updated and folks started updating their ports without = realizing >> that they have shot themselfs into the foot! >>=20 >=20 > Not reading UPDATING until there are problems is not the fault of the = ports > tree; it should be checked every time you update. >=20 > Of course, many of us forget, but that still doesn't make it anyone = else's > problem when we do! 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. = So, even though people check UPDATING, it won't help them because there = will be nothing apropos there until maybe days later when someone has = decided an UPDATING entry was merited in retrospect. I'm not sure what the solution is for the end user. I know I get = somewhat leery of updating my ports if I see a large number of changes = coming via portsnap (like the 4000+ that accompanied the recent libpng = upgrade) and there is nothing new in UPDATING (which, happily wasn't the = case with the libpng upgrade). Usually, I wait a while for the dust to = clear and an UPDATING entry potentially to appear. Maybe the solution is to track the freebsd-ports mailing list get get = advanced warning of large changes, but that would mean following another = high-volume list. :-( Cheers, Paul.