From owner-freebsd-stable@FreeBSD.ORG Sat Jun 2 18:56:03 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 A59B41065692 for ; Sat, 2 Jun 2012 18:56:03 +0000 (UTC) (envelope-from apeiron@isuckatdomains.net) Received: from isuckatdomains.net (unknown [IPv6:2600:3c01:e000:4::1]) by mx1.freebsd.org (Postfix) with ESMTP id 8B2898FC12 for ; Sat, 2 Jun 2012 18:56:03 +0000 (UTC) Received: from isuckatdomains.members.linode.com (isuckatdomains.net [74.207.243.179]) by isuckatdomains.net (Postfix) with ESMTPSA id 2097D45ABC for ; Sat, 2 Jun 2012 14:56:03 -0400 (EDT) Date: Sat, 2 Jun 2012 14:56:01 -0400 From: Chris Nehren To: freebsd-stable@freebsd.org Message-ID: <20120602185601.GD2309@isuckatdomains.members.linode.com> Mail-Followup-To: freebsd-stable@freebsd.org 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> <95D35900-AC63-4948-B54F-40041FFCB232@gromit.dlib.vt.edu> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <95D35900-AC63-4948-B54F-40041FFCB232@gromit.dlib.vt.edu> User-Agent: Mutt/1.5.21 (2010-09-15) 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:56:03 -0000 On Sat, Jun 02, 2012 at 14:11:06 -0400 , Paul Mather wrote: > 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. If you're concerned about things breaking, don't follow the bleeding edge. This seems to be common sense. > 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. :-( And any decent mailer setup can filter those messages for you, leaving only the messages relevant to ports you're interested in. There are also systems like gmane which provide an NNTP feed for mailing lists. Combined with a newsreader with good killfile / scoring features, it shouldn't be hard to keep up. -- Thanks and best regards, Chris Nehren