From owner-freebsd-ports Fri Dec 20 6: 3:43 2002 Delivered-To: freebsd-ports@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 937EB37B406 for ; Fri, 20 Dec 2002 06:03:42 -0800 (PST) Received: from albatross.prod.itd.earthlink.net (albatross.mail.pas.earthlink.net [207.217.120.120]) by mx1.FreeBSD.org (Postfix) with ESMTP id 210C343EE8 for ; Fri, 20 Dec 2002 06:03:42 -0800 (PST) (envelope-from rsidd@papagena.rockefeller.edu) Received: from user-0cev11k.cable.mindspring.com ([24.239.132.52] helo=bluerondo.a.la.turk) by albatross.prod.itd.earthlink.net with esmtp (Exim 3.33 #1) id 18PNkb-0006fs-02 for ports@freebsd.org; Fri, 20 Dec 2002 06:03:41 -0800 Received: (qmail 4204 invoked by uid 1001); 20 Dec 2002 14:03:37 -0000 Date: Fri, 20 Dec 2002 09:03:37 -0500 From: Rahul Siddharthan To: Maxim Sobolev Cc: portmgr@freebsd.org, ports@freebsd.org Subject: Re: Thoughts about ports freeze Message-ID: <20021220140337.GA4018@papagena.rockefeller.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.3.27i X-Operating-System: FreeBSD 4.7-STABLE i386 Sender: owner-freebsd-ports@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Maxim Sobolev wrote: > And I don't have a single good argument to reply to those > complains with - users usually don't care about 5.0, but they do care > about their 4.x production machines receiving latest updates and fixes, > and the current situation pisses them off. ... > What do people think? I think *something* should certainly be done -- the ports tree should be unfrozen, in whatever way possible. I love FreeBSD, but as of now I'm in the above category -- at the moment I don't care about 5.0 but I do want my 4.x updates. You're quite right about the current situation "pissing people off." If this continues, we can forget about ever popularizing "FreeBSD on the desktop." What about freezing some small "core" set of ports, say XFree86, a couple of window managers, a web browser, etc; and unfreezing the rest? Even for those ports, isn't it possible to freeze the 5.0 version (with an .if defined(...) ... .endif bracketing the entire frozen part for 5.0 only) and let the 4.x version evolve on its own? Thanks, Rahul To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-ports" in the body of the message