Date: Sat, 2 Jun 2012 21:50:22 +0200 From: Kurt Jaeger <lists@opsec.eu> To: freebsd-stable@freebsd.org Subject: Re: Why Are You NOT Using FreeBSD? Message-ID: <20120602195022.GG5335@home.opsec.eu> 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
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'. -- pi@opsec.eu +49 171 3101372 8 years to go !
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20120602195022.GG5335>