Date: Sun, 10 Oct 2004 17:03:31 -0400 From: Chuck Swiger <cswiger@mac.com> To: Dick Davies <rasputnik@hellooperator.net> Cc: FreeBSD Current <freebsd-current@freebsd.org> Subject: Re: ports freeze and portaudit alerts Message-ID: <4169A3A3.9070308@mac.com> In-Reply-To: <20041010204308.GA29900@lb.tenfour> References: <20041010204308.GA29900@lb.tenfour>
next in thread | previous in thread | raw e-mail | index | archive | help
Dick Davies wrote: > But I'm a little alarmed by the pre 5.3 release ports freeze - portaudit has > flagged an awful lot of packages as having holes and refused to install them. [ ... ] > I just wondered if there is a policy to not upgrade ports under any > circumstances, or if this is just an oversight? I can imagine this would make > me very twitchy if I was running production boxes during a freeze.... > or have I missed something, and this doesn't affect 4.* users? The ports freeze slows down the rate at which changes are made to ports, but important changes like security fixes will still happen, and permitted after approval from <portmgr@freebsd.org>. Your question prompts another, however, which is: "How long is too long to keep the ports tree frozen?" I suspect that there would exist less busywork between portmgr@ and maybe re@ if the ports tree was frozen not during the entire beta cycle, but starting a week or so before the RC versions come out. -- -Chuck
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4169A3A3.9070308>