From owner-freebsd-gnome@FreeBSD.ORG Fri Dec 24 17:17:19 2010 Return-Path: Delivered-To: gnome@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 9E6AD106566C for ; Fri, 24 Dec 2010 17:17:19 +0000 (UTC) (envelope-from mezz.freebsd@gmail.com) Received: from mail-fx0-f54.google.com (mail-fx0-f54.google.com [209.85.161.54]) by mx1.freebsd.org (Postfix) with ESMTP id 325CD8FC18 for ; Fri, 24 Dec 2010 17:17:19 +0000 (UTC) Received: by fxm16 with SMTP id 16so7710743fxm.13 for ; Fri, 24 Dec 2010 09:17:18 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:received:in-reply-to :references:date:message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=xs26D3rFvUxpDXLIyHsa7gg0REUOxViAwN3OJ5Ne1jQ=; b=s9T26Z9yc7cprQhVGsPSCn/tpP+wstINkNfxFev4RIK4gufIT42FJZXIsBcFBFYOH1 A2FUR+RGR6EckkQ32EDm6U2eIMqOb0wuTU9cEHdHFmGYIvbN/zZxBGGQ6mJqdHJ8NVRj tI8Ls9pfxKCOSkzqGWz+goAth6FzH/dX9CWkA= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; b=PogLVaztJh9LKHJa+zRdj0ntkqxeEYaLQHfRlZ2a20SjQrRQ/GI7KZ6bONROtWPFk0 DRAof1aB3+Q/9Rt0fXP4y5+39/LnS/J30zGXuIYiiaZu5Lr1HHBL6O83/DEEbk26rCXF YOqTbycAYJmBqKEIjenoYFCucbSejp/wgXYdw= MIME-Version: 1.0 Received: by 10.223.93.137 with SMTP id v9mr2531601fam.85.1293211037032; Fri, 24 Dec 2010 09:17:17 -0800 (PST) Received: by 10.223.97.80 with HTTP; Fri, 24 Dec 2010 09:17:16 -0800 (PST) In-Reply-To: <61450.1293149872@tristatelogic.com> References: <61450.1293149872@tristatelogic.com> Date: Fri, 24 Dec 2010 11:17:16 -0600 Message-ID: From: Jeremy Messenger To: "Ronald F. Guilmette" Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Cc: gnome@freebsd.org Subject: Re: ports/153300: configure error for misc/shared-mime-info-0.80 X-BeenThere: freebsd-gnome@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: GNOME for FreeBSD -- porting and maintaining List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 24 Dec 2010 17:17:19 -0000 On Thu, Dec 23, 2010 at 6:17 PM, Ronald F. Guilmette wrote: > > In message = , you > wrote: > >>On Thu, Dec 23, 2010 at 2:02 AM, Ronald F. Guilmette >> wrote: >>> >>> In message <201012201634.oBKGY97Q083871@freefall.freebsd.org>, you wrot= e: >>> >>>>Synopsis: configure error for misc/shared-mime-info-0.80 >>>> >>>>State-Changed-From-To: open->closed >>>>State-Changed-By: mezz >>>>State-Changed-When: Mon Dec 20 16:33:16 UTC 2010 >>>>State-Changed-Why: >>>>Not missing dependency, because it already depends on perl stuff. It so= unds >>>>like you didn't follow the Perl upgrade in /usr/ports/UPDATING. You nee= d to >>>>reinstall all ports that depend on Perl and it will solve your issue. >>>> >>>>http://www.freebsd.org/cgi/query-pr.cgi?pr=3D153300 >>> >> >>> Because of this seemingly pervasive problem, I think that you should >>> give some consideration to re-opening this PR. >> >>No need to. >> >>> On the other hand, if I am wrong about any part of my analysis, then by >>> all means, please do enlighten me as to where I have gone wrong. >> >> >>You have analysis it perfectly for what kind of problem you have. Only >>a problem is that you didn't follow in the /usr/ports/UPDATING that >>was documented about what you need to do to update your icu. > > Uggg. =A0OK. =A0My bad. =A0You're right. =A0I didn't see that item in the= re. > (Maybe I can be forgiven for this particylar faux pas... that UPDATING > document is now over 10,000 lines long. =A0Does everyone actually read > 100% of that??) > > In any case, I would still like to understand why it is the case that I > need to make this extra special effort to run "portupgrade -fr devel/icu"= . > In other words, why haven't all of the port dependencies been arranged in > such a way so that "portupgrade -a" would not have achieved the same effe= ct? Because of libtool or/and pkg-config issue. Same problem even in the Linux world. Some applications don't need to be linked with some libraries, but did anyway because of flag is in one of *.la file or/and pkg-config. We have a hack in bsd.gnome.mk called ltasneededhack that can help with this issue, but it requires a careful test to make sure it's stable on each ports if it works. The ltasneededhack will helping to not get link with library when it's not need to be. There is better explain in the mailing list archive somewhere that I can't find at the moment. > Why do I have to _force_ rebuilds of everything depending on icu? =A0Why > don't all those rebuilds just occur automatically from "portupgrade -a"? > > My apologies if I am asking FAQs, but I obviously don't understand > something fundamental here, and I'd like to. > > Should I assume that "portupgrade -a" only rebuilds those ports whose > version numbers have changed in the ports tree, and that it ignores > cases where the port version is unchanged and where some _other_ port > that the given port depends on has been changed/upgraded? > > If so, then maybe a nice addition to portupgrade would be a new option > that does what -a does _and_ that also forces the upgrade of any port `A' > which depends upon any other port `B' whose version has changed (i.e. > since port `a' was last built/installed). Both portupgrade and portmaster have option to put your old library in the /usr/local/lib/compat/pkg/ that way your non-rebuilt ports still can use it until you finish with the rebuilt. Cheers, Mezz > Does that seem reasonable? > > > Regards, > rfg --=20 mezz.freebsd@gmail.com - mezz@FreeBSD.org FreeBSD GNOME Team http://www.FreeBSD.org/gnome/ - gnome@FreeBSD.org