From owner-freebsd-stable@FreeBSD.ORG Sat Jun 2 17:31:49 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 8EA801065675; Sat, 2 Jun 2012 17:31:49 +0000 (UTC) (envelope-from utisoft@gmail.com) Received: from mail-bk0-f54.google.com (mail-bk0-f54.google.com [209.85.214.54]) by mx1.freebsd.org (Postfix) with ESMTP id D65C28FC24; Sat, 2 Jun 2012 17:31:48 +0000 (UTC) Received: by bkvi18 with SMTP id i18so3450860bkv.13 for ; Sat, 02 Jun 2012 10:31:47 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=4BThL3r1GjNy3q6WjqPQA2t564euGTXFPOlRYs6iLo0=; b=GcVIEoZAu3VZj5xTFNUvIA9xWHi0hLxWQ70IbcAPwilLzly/aOwQLjX/zcsx/3z7gf O6QcnaY2YBcsk3as5WDSYMWtokUAwDvSUmFmPMW/okwalr3U+1Elpy0CQ8PLG9cXeDBG R2fnkeV3b/e0M6/1Ek2qsdAEitBcjvArKoMc799GSdzUjc8257HTdixYhtWyEgQ82WoE LFkH6rw/VWiiGeqZcybkSIO6YYVbca8h8fi5ziaIjG6dGhcHuWcXFTqj9Xsju5UB33+P IWBq1i6feKVsb8BJ/1vySpWbYCgTfOjFItzKzfQuqufInZzqUW2HDMJB7G0O0dGN5+8/ XI6Q== MIME-Version: 1.0 Received: by 10.205.117.3 with SMTP id fk3mr3943519bkc.136.1338658307567; Sat, 02 Jun 2012 10:31:47 -0700 (PDT) Received: by 10.204.171.138 with HTTP; Sat, 2 Jun 2012 10:31:47 -0700 (PDT) Received: by 10.204.171.138 with HTTP; Sat, 2 Jun 2012 10:31:47 -0700 (PDT) In-Reply-To: <4FCA20C5.6010901@zedat.fu-berlin.de> 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> Date: Sat, 2 Jun 2012 18:31:47 +0100 Message-ID: From: Chris Rees To: "O. Hartmann" Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: freebsd-current , FreeBSD 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 17:31:49 -0000 On Jun 2, 2012 3:19 PM, "O. Hartmann" 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