Skip site navigation (1)Skip section navigation (2)
Date:      Sat, 2 Jun 2012 18:31:47 +0100
From:      Chris Rees <utisoft@gmail.com>
To:        "O. Hartmann" <ohartman@zedat.fu-berlin.de>
Cc:        freebsd-current <freebsd-current@freebsd.org>, FreeBSD <freebsd-stable@freebsd.org>
Subject:   Re: Why Are You NOT Using FreeBSD?
Message-ID:  <CADLo83-7VvmBOnG=%2Bm7q2MKyYOe-YoE=ctqFEfzZJVuEdk8VGQ@mail.gmail.com>
In-Reply-To: <4FCA20C5.6010901@zedat.fu-berlin.de>
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>

next in thread | previous in thread | raw e-mail | index | archive | help
On Jun 2, 2012 3:19 PM, "O. Hartmann" <ohartman@zedat.fu-berlin.de> wrote:
>
> On 06/02/12 14:47, Daniel Kalchev wrote:
> >
> >
> > 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.
> >>
> >> Or do I see this really too simple?
> >
> > 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 :)
> >
> > Daniel
>
> 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!
>

Not reading UPDATING until there are problems is not the fault of the ports
tree; it should be checked every time you update.

Of course, many of us forget, but that still doesn't make it anyone else's
problem when we do!

Chris



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CADLo83-7VvmBOnG=%2Bm7q2MKyYOe-YoE=ctqFEfzZJVuEdk8VGQ>