From owner-freebsd-current Fri Oct 18 14:16:25 2002 Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 3BA6637B401; Fri, 18 Oct 2002 14:16:24 -0700 (PDT) Received: from albatross.prod.itd.earthlink.net (albatross.mail.pas.earthlink.net [207.217.120.120]) by mx1.FreeBSD.org (Postfix) with ESMTP id C198643E8A; Fri, 18 Oct 2002 14:16:23 -0700 (PDT) (envelope-from tlambert2@mindspring.com) Received: from pool0209.cvx21-bradley.dialup.earthlink.net ([209.179.192.209] helo=mindspring.com) by albatross.prod.itd.earthlink.net with esmtp (Exim 3.33 #1) id 182eSW-00048n-00; Fri, 18 Oct 2002 14:15:05 -0700 Message-ID: <3DB07991.2228642D@mindspring.com> Date: Fri, 18 Oct 2002 14:13:53 -0700 From: Terry Lambert X-Mailer: Mozilla 4.79 [en] (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: "Long, Scott" Cc: 'Kris Kennaway' , Scott Long , current@freebsd.org, ports@freebsd.org Subject: Re: cdrtools doesn't build on -current References: <6100BCEB85F8E244959C756C04E0EDD161CAD8@otcexc01.otc.adaptec.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG "Long, Scott" wrote: > Yes, I'm sorry if it sounded like I was picking on the ports committers. > Changes due to standards compliance, architecture changes, etc, all > wreak havoc on ports, and hopefully the pace of that will slow down. > Unfortunately, the direction of FreeBSD is what it is, and the onus is > on the ports maintainers to keep their ports up to date and working. Actually, the onus is on the people who changed the code on which the port depended to hide behind something large, while everyone who used the port throws large and very pointy rocks. Standards compliance is a marginally valid argument for change; architectural changes which do not maintain backward compatability are much less so -- particularly if the failure to maintain the compatability was not an unavoidable consequence of the change: it's not fair to deprecate interfaces without a compatability period, or at least some warning other than "Hey! Everyone should be running my experimental code to shake at any bugs, 'cause I'm too lazy!". -- Terry To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message