From owner-freebsd-ports@FreeBSD.ORG  Fri Aug  7 01:34:30 2009
Return-Path: <owner-freebsd-ports@FreeBSD.ORG>
Delivered-To: freebsd-ports@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
	by hub.freebsd.org (Postfix) with ESMTP id C5F341065689
	for <freebsd-ports@freebsd.org>; Fri,  7 Aug 2009 01:34:30 +0000 (UTC)
	(envelope-from erich@apsara.com.sg)
Received: from babylon.webvis.net (babylon.webvis.net [202.157.163.226])
	by mx1.freebsd.org (Postfix) with ESMTP id 2DDD48FC32
	for <freebsd-ports@freebsd.org>; Fri,  7 Aug 2009 01:34:29 +0000 (UTC)
Received: from [10.0.1.240] ([119.73.191.194]) by apsara.com.sg ;
	Fri, 07 Aug 2009 09:34:24 +0800 SGT
From: Erich Dollansky <erich@apsara.com.sg>
Organization: apsara green technology pte ltd
To: "b. f." <bf1783@googlemail.com>
Date: Fri, 7 Aug 2009 09:34:20 +0800
User-Agent: KMail/1.9.10
References: <d873d5be0908061744p5ad99a79o853f46e1a6c7ea33@mail.gmail.com>
In-Reply-To: <d873d5be0908061744p5ad99a79o853f46e1a6c7ea33@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain;
  charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Message-Id: <200908070934.22472.erich@apsara.com.sg>
Cc: freebsd-ports@freebsd.org
Subject: Re: Ports completely and permanently hosed
X-BeenThere: freebsd-ports@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Porting software to FreeBSD <freebsd-ports.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-ports>,
	<mailto:freebsd-ports-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-ports>
List-Post: <mailto:freebsd-ports@freebsd.org>
List-Help: <mailto:freebsd-ports-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-ports>,
	<mailto:freebsd-ports-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Fri, 07 Aug 2009 01:34:32 -0000

Hi,

On 07 August 2009 am 08:44:44 b. f. wrote:
> Erich Dollansky wrote:
> >I think that you hit the weakest point of FreeBSD. When a
> > version number of a base port changes, hundreds or even
> > thousands of ports have to be recompiled. It is basically the
> > same effect as when the major version number of FreeBSD
> > changes.
>
> The same is true of almost any build-from-source distribution
> that uses shared libraries, not just FreeBSD.
>
of course, this is plain logic.

> >If this would be synchronised with the main FreeBSD releases,
> > it would have a minor effect on users.
>
> But please don't attempt to slow needed development by making
> *(&@Q%#%@!!!! suggestions like this.  If you need a seat-belt,
> put it on -- but don't wrap it around everyone's neck.
>
So, why is there a ports freeze just before a new release?

Isn't it done just out of the same reason?

They want to have a stable ports tree on the day of the release.

As I said, my seatbelt is the freeze whenever a basic library gets 
changed.

Erich
> b.