From owner-freebsd-ports@FreeBSD.ORG Sat Feb 1 07:14:32 2014 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id E4428D3A; Sat, 1 Feb 2014 07:14:32 +0000 (UTC) Received: from mail.bsdbox.co (122-149-22-79.static.dsl.dodo.com.au [122.149.22.79]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 979C115DB; Sat, 1 Feb 2014 07:14:31 +0000 (UTC) Received: from [10.0.0.4] (122-149-22-79.static.dsl.dodo.com.au [122.149.22.79]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.bsdbox.co (Postfix) with ESMTPSA id 827A0893ED; Sat, 1 Feb 2014 07:14:29 +0000 (UTC) Message-ID: <52EC9ED4.6030604@bsdbox.co> Date: Sat, 01 Feb 2014 18:14:28 +1100 From: nano User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.2.0 MIME-Version: 1.0 To: Guido Falsi , freebsd-ports@freebsd.org Subject: Re: libiconv on 10.0-RELEASE References: <52EC99E0.2080801@bsdbox.co> <52EC9C3D.6060505@FreeBSD.org> In-Reply-To: <52EC9C3D.6060505@FreeBSD.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 01 Feb 2014 07:14:33 -0000 On 1/02/2014 6:03 PM, Guido Falsi wrote: > On 02/01/14 07:53, nano wrote: >> Seems to be some issues with it: >> https://forums.freebsd.org/viewtopic.php?f=5&t=44644 >> https://forums.freebsd.org/viewtopic.php?f=5&t=44659 >> >> And my problem: >> https://forums.freebsd.org/viewtopic.php?f=5&t=44658 >> >> Can't do UPDATING: 20130904, libiconv has never been on the system. >> >> Not sure whether to allow portmaster to upgrade[*]. Pretty sure >> something will break if I do. What do you suggest? > > Hi, > > Since then a new commit has changed things a little, it's r341775 [1] > > It now allows libiconv to be installed by a few selected ports who > really need functionality not available in the base implementation of > iconv. > >> >> >> [*] >> # portmaster -adwv >> ===>>> All >> (4) >> >> ===>>> The following actions will be taken if you choose to proceed: >> Upgrade php55-iconv-5.5.8 to php55-iconv-5.5.8_1 >> Install converters/libiconv >> Upgrade nginx-1.4.4_2,1 to nginx-1.4.4_3,1 >> Upgrade owncloud-6.0.0a to owncloud-6.0.1 >> >> ===>>> Proceed? y/n [y] n >> >> > > From what I see here I think you can allow it to do that without > problems for now. I've seen two PRs stating problems with some ports. > > The PRs I've indicate that, after such a step, glib20 and exim fail to > build. These problems need fixing at present. > > This applies only to ports compiled on the live system, if one is using > poudriere or tinderbox they can build anyway(so binary packages have no > problems), this happens because when using these software each port is > compiled in a clean environment. > > [1] http://svnweb.freebsd.org/ports?view=revision&revision=341775 > Hi, Guido. Thanks for your response. Not sure about this users particular situation, except that it appears they are experiencing some problems compiling libiconv [0]. Another user seems to be experiencing problems (re)installing php5x-iconv, which has rendered something broken [1]. This makes me reluctant to proceed with my upgrades for fear that similar will occur. Also, I'm not usng svn, but portsnap; don't know if it matches r341775. I appreciate your advice, but I think I will wait before updating these ports. Hopefully things get cleaned up a bit. I would not be happy if something breaks. [0] http://forums.freebsd.org/viewtopic.php?f=5&t=44644&p=248807#p248731 [1] http://forums.freebsd.org/viewtopic.php?f=5&t=44659#p248806 -- bsdbox.co