Date: Sat, 2 Jun 2012 14:56:01 -0400 From: Chris Nehren <apeiron+freebsd-stable@isuckatdomains.net> To: freebsd-stable@freebsd.org Subject: Re: Why Are You NOT Using FreeBSD? Message-ID: <20120602185601.GD2309@isuckatdomains.members.linode.com> In-Reply-To: <95D35900-AC63-4948-B54F-40041FFCB232@gromit.dlib.vt.edu> References: <C480320C-0CD9-4B61-8AFB-37085C820AB7@FreeBSD.org> <1405746.nVtAo183hi@x220.ovitrap.com> <4FC9FECC.8090703@digsys.bg> <3303845.JjFTmctz7f@x220.ovitrap.com> <4FCA0B5F.5010500@digsys.bg> <4FCA20C5.6010901@zedat.fu-berlin.de> <CADLo83-7VvmBOnG=%2Bm7q2MKyYOe-YoE=ctqFEfzZJVuEdk8VGQ@mail.gmail.com> <95D35900-AC63-4948-B54F-40041FFCB232@gromit.dlib.vt.edu>
next in thread | previous in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20120602185601.GD2309>