From owner-freebsd-ports@FreeBSD.ORG Sat Mar 10 06:47:14 2007 Return-Path: X-Original-To: freebsd-ports@freebsd.org Delivered-To: freebsd-ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 8CAE916A402 for ; Sat, 10 Mar 2007 06:47:14 +0000 (UTC) (envelope-from dougb@FreeBSD.org) Received: from mail2.fluidhosting.com (mx24.fluidhosting.com [204.14.89.7]) by mx1.freebsd.org (Postfix) with SMTP id EFF1513C428 for ; Sat, 10 Mar 2007 06:47:13 +0000 (UTC) (envelope-from dougb@FreeBSD.org) Received: (qmail 15443 invoked by uid 399); 10 Mar 2007 06:47:13 -0000 Received: from localhost (HELO lap.dougb.net) (dougb@dougbarton.us@127.0.0.1) by localhost with SMTP; 10 Mar 2007 06:47:13 -0000 X-Originating-IP: 127.0.0.1 Message-ID: <45F2546F.60401@FreeBSD.org> Date: Fri, 09 Mar 2007 22:47:11 -0800 From: Doug Barton Organization: http://www.FreeBSD.org/ User-Agent: Thunderbird 2.0b2 (X11/20070116) MIME-Version: 1.0 To: Ade Lovett References: <45F1DDE2.5030404@FreeBSD.org> <45F1EA6A.6070904@FreeBSD.org> <20070310023034.c5939c48.jylefort@FreeBSD.org> <7CF1749C-3254-46AC-ABDD-BAB0D84ED7A1@FreeBSD.org> In-Reply-To: <7CF1749C-3254-46AC-ABDD-BAB0D84ED7A1@FreeBSD.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: Jean-Yves Lefort , Kent Stewart , freebsd ports Subject: Re: Ports 104877 causing big problems 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: Sat, 10 Mar 2007 06:47:14 -0000 Ade Lovett wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > > On Mar 09, 2007, at 17:30 , Jean-Yves Lefort wrote: > >> On Fri, 9 Mar 2007 17:05:31 -0800 >> Ade Lovett wrote: >>> 3. Ports that *are* affected by this issue (assuming the issue still >>> exists) can be fixed in a more relaxed manner (eg: a conversion of >>> GNU_CONFIGURE=YES to USE_AUTOTOOLS=configurehack [implying >>> GNU_CONFIGURE=YES]) than a time-T switch. It will also allow for >>> such affected ports to have PORTREVISIONs bumped by the respective >>> maintainers so as to more clearly identify improved operation to the >>> consumers of those ports. >> >> All ports that use libtool to produce a program or shared library are >> affected by this issue. > > This in turn implies that in case that there is an issue, and something > needs to be done about it, then silently changing the semantics of > GNU_CONFIGURE is not an appropriate solution. In order for the change, > should it be required, to be communicated to all the consumers of the > FreeBSD ports tree, and not that subset that happens to read esoteric > discussions on a high volume mailing list, this requires that we use the > tools available to us, ie: bumping PORTREVISION. On it's face I find the idea of bumping PORTREVISION for every port that uses libtool in any form a sort of silly proposition. The change in behavior was introduced in Mk/*, I think it's reasonable to expect that the fix happen there too. > 1. Identify if there is still a problem. I just performed the following experiment. Please let me know if you think this constitutes empirical evidence of a problem. 1. csup'ed to the latest ports tree 2. Saved a copy of /var/db/pkg/libgpg-error-1.4/+REQUIRED_BY 3. pkg_delete'd mtr-0.72, which was listed in the +REQUIRED_BY file 4. Checked the file, mtr was gone. 5. Built and installed mtr 6. mtr is back in /var/db/pkg/libgpg-error-1.4/+REQUIRED_BY There is no reason that mtr would need libgpg-error, and there is no dependency for it in the Makefile. It does however set GNU_CONFIGURE. > 2b. If yes, add a new stanza to USE_AUTOTOOLS, for simplicities sake > we'll call it lthack, which defines GNU_CONFIGURE, and also wanders > through the configuration files performing the appropriate hackery. I don't think this is reasonable, or realistic. It would require that every single port which uses GNU_CONFIGURE gets changed. > 3. Maintainers that have ports affected by the issue go in to the > Makefile, chunk GNU_CONFIGURE, add USE_AUTOTOOLS= lthack, bump > PORTREVISION, and move on to the next one. The burden for fixing problems caused by the infrastructure should not be placed on maintainers generally. Specifically, this problem is too widespread, too nasty, and too urgently in need of a fix to warrant the delays that asking maintainers to make these changes would cause. If a short term fix that is less elegant needs to happen now so that time can be spent on a more elegant one in the longer term, so be it. Doug -- This .signature sanitized for your protection