Skip site navigation (1)Skip section navigation (2)
Date:      Sun, 4 Nov 2012 23:54:43 +0100
From:      "C-S" <>
Subject:   Re: before new version
Message-ID:  <>
In-Reply-To: <>
References:  <>

Next in thread | Previous in thread | Raw E-Mail | Index | Archive | Help
> Date: Sat, 3 Nov 2012 17:20:26 -0500
> From: ajtiM <>
> To: Polytropon <>
> Cc:
> Subject: Re: before new version
> Message-ID: <>
> Content-Type: Text/Plain;  charset="iso-8859-1"
> On Saturday 03 November 2012 14:11:22 you wrote:
>> > BTW: packages are almost all the time outdated.
>> The packages in the RELEASE directory and on the installation
>> media meet the frozen ports tree (frozen _prior_ to the release
>> date), so yes, they are a bit outdated, but they are considered
>> "mostly stable and usable" when in use with what is distributed.
>> On the server, both _those_ packages _and_ those in Latest/ (which
>> are periodically built from the "advancing" ports tree after the
>> release date) are often considered not _that_ current as if you
>> would use CVS or SVN to obtain the "bleeding edge" latest ports
>> tree and build from source.
> I didn't complain about "bleeding edge" sofware which we anywhere don't
> have
> (Gimp, Xorg, LibreOffice and all dependencies for those applications and
> more
> and more which I don't use and I don't need) but I complain about freezing
> ports too early before new release came out and after that rebuilt 5000
> ports
> for example just because png new version is coming out. Or am I wrong?
>> So yes, you could say what you said. :-)
> Mitja
> --------

Your complaint seems to be unfair to me as this is the first time -- as
far as I remember -- that the ports freeze was implemented only for RC2
but not already for RC1. So, the tree is certainly not frozen "too


Want to link to this message? Use this URL: <>