From owner-freebsd-ports@FreeBSD.ORG Mon Jul 23 01:22:49 2012 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx2.freebsd.org (mx2.freebsd.org [69.147.83.53]) by hub.freebsd.org (Postfix) with ESMTP id 5DE52106566C; Mon, 23 Jul 2012 01:22:49 +0000 (UTC) (envelope-from dougb@FreeBSD.org) Received: from opti.dougb.net (hub.freebsd.org [IPv6:2001:4f8:fff6::36]) by mx2.freebsd.org (Postfix) with ESMTP id 4637414ED7E; Mon, 23 Jul 2012 01:22:48 +0000 (UTC) Message-ID: <500CA767.2020206@FreeBSD.org> Date: Sun, 22 Jul 2012 18:22:47 -0700 From: Doug Barton Organization: http://SupersetSolutions.com/ User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:13.0) Gecko/20120621 Thunderbird/13.0.1 MIME-Version: 1.0 To: Jeremy Messenger References: <15617903.FBMimp13fy@mocha.verizon.net> <2193820.CL19acAFmS@mocha.verizon.net> <500B1953.10809@FreeBSD.org> <500B8811.9090609@FreeBSD.org> <500C6DA9.1070305@FreeBSD.org> In-Reply-To: X-Enigmail-Version: 1.4.2 OpenPGP: id=1A1ABC84 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: Scot Hetzel , kde@freebsd.org, ruby@freebsd.org, Edwin Groothuis , freebsd-ports@freebsd.org, gnome@freebsd.org, "Jason E. Hale" Subject: Re: How to remove erroneous deps from pkgng 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, 23 Jul 2012 01:22:49 -0000 On 07/22/2012 17:50, Jeremy Messenger wrote: > On Sun, Jul 22, 2012 at 4:16 PM, Doug Barton wrote: >> On 07/22/2012 07:51, Jeremy Messenger wrote: >>> You need to start to respect the people's work and plan, Doug. Also I >>> am part of team that maintaining the bsd.gnome.mk. Yes it will be >>> re-add if anyone plan to remove it, because I already have planned add >>> the :build/:run feature in the bsd.gnome.mk that the without :* will >>> be both build/run time dependency. It is impossible for me to not >>> re-add it. It is not going to be long because I already have function >>> :build/:run in the bsd.mate.mk (was repocopied from bsd.gnome.mk) >>> available. >>> >>> The only thing that I don't plan is to chase thousands of port to have >>> the 'pkgconfig;build'. If anyone want to take up this task is cool >>> with me. >> >> So what you're saying is that in spite of the fact that the community >> has identified a bug that it wants to fix, a bug which was added by the >> team maintaining bsd.gnome.mk, that you are refusing to modify your >> patch to handle the bug; but instead are demanding your right to >> reintroduce the bug, and then further demanding the right to not fix it >> after the patch is in? > > Remove the runtime dependency is a bug either because there are a few > that need it in the runtime dependency. Which ports are those? And even if these ports exist, an explicit run dep can be added for them. Better to add one more dep for a few ports than bogus ones for thousands. > I have written a best solution > than remove that runtime line. It will be 99% bug free when all ports > have the right :build/:run. I'm interested in your feedback to Max' point that the equivalent functionality for kde.mk already has the right logic to handle proper defaults if the right :label isn't set. >> And furthermore, you're refusing to even look at >> the other dependencies which are handled by bsd.gnome.mk to see if >> similar bugs were introduced *by your team*, but you're happy to let >> everyone else sort out the problems in thousands of ports for you. > > Quiet simple, I do not have time for that huge project. That's fine, stand aside and let people who are willing to solve the problem properly do the work. Then when your patch is in proper shape it can be committed without fear of adding new bugs, or re-adding old ones. The position you're taking that we can't fix the bug because you demand your right to get *your* patch in is entirely unreasonable. Doug -- Change is hard.