From owner-cvs-ports@FreeBSD.ORG Tue Apr 13 08:43:34 2004 Return-Path: Delivered-To: cvs-ports@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D0B7D16A4CE; Tue, 13 Apr 2004 08:43:34 -0700 (PDT) Received: from mail.soaustin.net (mail.soaustin.net [207.200.4.66]) by mx1.FreeBSD.org (Postfix) with ESMTP id AF07243D2F; Tue, 13 Apr 2004 08:43:32 -0700 (PDT) (envelope-from linimon@lonesome.com) Received: by mail.soaustin.net (Postfix, from userid 502) id 5C98B140DA; Tue, 13 Apr 2004 10:43:32 -0500 (CDT) Date: Tue, 13 Apr 2004 10:43:32 -0500 (CDT) From: Mark Linimon X-X-Sender: linimon@pancho To: Alexey Dokuchaev In-Reply-To: <20040413152837.GA94022@regency.nsu.ru> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: cvs-ports@freebsd.org cc: Erwin Lansing cc: cvs-all@freebsd.org cc: ports-committers@freebsd.org Subject: Re: cvs commit: CVSROOT modules X-BeenThere: cvs-ports@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: CVS commit messages for the ports tree List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 13 Apr 2004 15:43:35 -0000 On Tue, 13 Apr 2004, Alexey Dokuchaev wrote: > Just out of curiosity, why not just make this port build and run > properly under both FreeBSD stable & current, and leave the port in? An excellent idea ... one which no one stepped up to do during the 2-month period between when it was first proposed for removal, and it was actually removed. (FWIW, I was the person who proposed it). The problem is that we have more ports that are broken on -current than we have volunteers to fix them (right now the count is around 400 on both amd64 and ia64; a little bit lower on the others). At some point in the not-too-distant future we're going to make what is now -current into the "new -stable". When that happens, IMHO we're going to have a lot of unhappy users who waste time trying to build ports that will not run on their systems, who are on the one hand told "you should upgrade", and on the other hand, "well, yeah, but 4% of the ports will no longer work". Summary: I'd rather see broken ports fixed than deleted, but at some point (again IMHO) we really have to do one or the other. Otherwise we just run the risk of letting users waste their time. mcl