From owner-freebsd-ports@FreeBSD.ORG Mon Dec 3 10:20:30 2007 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id F1E3716A41B for ; Mon, 3 Dec 2007 10:20:30 +0000 (UTC) (envelope-from ade@lovett.com) Received: from mail.lovett.com (foo.lovett.com [67.134.38.158]) by mx1.freebsd.org (Postfix) with ESMTP id DC49013C474 for ; Mon, 3 Dec 2007 10:20:30 +0000 (UTC) (envelope-from ade@lovett.com) Received: from inferno.canal.lovett.com ([172.16.32.23]:64802) by mail.lovett.com with esmtpsa (TLSv1:AES128-SHA:128) (Exim 4.68 (FreeBSD)) (envelope-from ) id 1Iz7vY-000ESO-LO; Mon, 03 Dec 2007 01:49:24 -0800 Message-Id: From: Ade Lovett To: Aryeh M. Friedman In-Reply-To: <4753C9EA.4060705@gmail.com> Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes Content-Transfer-Encoding: 7bit Mime-Version: 1.0 (Apple Message framework v915) Date: Mon, 3 Dec 2007 01:49:23 -0800 References: <20071201204245.GA57218@lpthe.jussieu.fr> <20071201221533.GU50167@server.vk2pj.dyndns.org> <4751E4F3.9010603@gmail.com> <200712030302.51908.josh@tcbug.org> <4753C9EA.4060705@gmail.com> X-Mailer: Apple Mail (2.915) Sender: ade@lovett.com Cc: freebsd-ports@freebsd.org Subject: Re: duration of the ports freeze X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 03 Dec 2007 10:20:31 -0000 On Dec 03, 2007, at 01:18 , Aryeh M. Friedman wrote: I'm probably going to regret joining this thread, but quite frankly, the amount of horse being thrown around has gotten way out of hand. > I have practical knowledge here in working with different dependency > management systems (which is essentially what the ports system is)... > now that being said much of it is based on seeing how different people > have solved the problems raised by the methods you site as being > "invalid" Fine. Prove your practical knowledge. Take a small subset of the ports tree, x11/xorg springs to mind, bang around a few ideas, show why they're "better", and we'll take it from there. Interminable threads about "why sucks", "why is better", "why don't you do it with " gets nowhere. Even a cursory glance at the archives of this mailing list would show that. > That is the purpose of the survey I sent out to start to uncover what > exactly the strengths and weaknesses are and decide if the weaknesses > are sufficent to warrent any kind of re-engineering. Unfortunately, as with most surveys, it suffers from a fundamental flaw in that it is self-selecting. It has gone out to that tiny subset of folks that: (a) use FreeBSD (b) use FreeBSD ports/packages (c) subscribe to ports@FreeBSD.org (d) feel like filling out a survey By my reckoning, just those 4 points have deselected at *least* 99% of folks that would potentially benefit from *any* kind of reworking. Hopefully, y'all will take this as constructive criticism from someone that (a) actually really does give a damn about FreeBSD/ports and (b) spends a lot of time, in conjunction with others, doing heavy-lifting infrastructural changes that aren't eye-candy. Around here, action, and not words, are taken much more seriously. We've heard the words before (albeit dressed and dolled up in a myriad of different way). Y'all are *not* going to get a (potential) rewrite of the ports system right first time. 18k+ ports, 4 different OS versions, at least 5 "useful" architectures. You do the math. Set up a wiki somewhere. Announce it to the community at large (hint, that means more than sending mails to @FreeBSD.org mailing lists). Put up some proposals (at this point, it really doesn't matter how hair-brained they might be). Let folks contribute in terms of editing. See what comes out of it. Highly restrictive mailing lists are *not* the right medium here. -aDe