From owner-freebsd-ports@FreeBSD.ORG  Fri Aug  7 02:22:20 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 D27821065672
	for <freebsd-ports@freebsd.org>; Fri,  7 Aug 2009 02:22:20 +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 2A3F28FC08
	for <freebsd-ports@freebsd.org>; Fri,  7 Aug 2009 02:22:19 +0000 (UTC)
Received: from [10.0.1.240] ([119.73.191.194]) by apsara.com.sg ;
	Fri, 07 Aug 2009 10:22:18 +0800 SGT
From: Erich Dollansky <erich@apsara.com.sg>
Organization: apsara green technology pte ltd
To: freebsd-ports@freebsd.org
Date: Fri, 7 Aug 2009 10:22:20 +0800
User-Agent: KMail/1.9.10
References: <d873d5be0908061744p5ad99a79o853f46e1a6c7ea33@mail.gmail.com>
	<200908070934.22472.erich@apsara.com.sg>
	<d873d5be0908061914k31c03364y6c4283dce8c842df@mail.gmail.com>
In-Reply-To: <d873d5be0908061914k31c03364y6c4283dce8c842df@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain;
  charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Message-Id: <200908071022.21530.erich@apsara.com.sg>
Cc: "b. f." <bf1783@googlemail.com>
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 02:22:22 -0000

Hi,

On 07 August 2009 am 10:14:25 b. f. wrote:
> On 8/7/09, Erich Dollansky <erich@apsara.com.sg> wrote:
> > On 07 August 2009 am 08:44:44 b. f. wrote:
> >> Erich Dollansky wrote:

> >> >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.
>
> Yes, and for building a stable subset of packages beforehand to
> ship with the release.  But these freezes are considered to be
> a necessary evil, to be removed as soon as possible, and not
> something that should be in place from release to release. The
> current version of the Ports tree is supposed to be the leading
> edge of (downstream) development.
>
You misunderstand me. I do not want a freeze of the ports tree, I 
only recommend, to either delay an update of a base port to the 
next freeze or put a short freeze around during which only ports 
are updated which got screwed by the change.

If I want a freeze to 'my' ports tree, I keep the one from the 
last release.

Erich