From owner-freebsd-ports@FreeBSD.ORG Sat Feb 1 07:03: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 38856B58 for ; Sat, 1 Feb 2014 07:03:32 +0000 (UTC) Received: from winston.madpilot.net (winston.madpilot.net [78.47.75.155]) by mx1.freebsd.org (Postfix) with ESMTP id E92961538 for ; Sat, 1 Feb 2014 07:03:31 +0000 (UTC) Received: from winston.madpilot.net (localhost [127.0.0.1]) by winston.madpilot.net (Postfix) with ESMTP id 3fGR8y5Cn0zFTB3; Sat, 1 Feb 2014 08:03:30 +0100 (CET) Received: from winston.madpilot.net ([127.0.0.1]) by winston.madpilot.net (winston.madpilot.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id lqb--6fcjmy5; Sat, 1 Feb 2014 08:03:28 +0100 (CET) Received: from tommy.madpilot.net (micro.madpilot.net [88.149.173.206]) by winston.madpilot.net (Postfix) with ESMTPSA; Sat, 1 Feb 2014 08:03:28 +0100 (CET) Message-ID: <52EC9C3D.6060505@FreeBSD.org> Date: Sat, 01 Feb 2014 08:03:25 +0100 From: Guido Falsi User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:24.0) Gecko/20100101 Thunderbird/24.2.0 MIME-Version: 1.0 To: nano , freebsd-ports@freebsd.org Subject: Re: libiconv on 10.0-RELEASE References: <52EC99E0.2080801@bsdbox.co> In-Reply-To: <52EC99E0.2080801@bsdbox.co> Content-Type: text/plain; charset=us-ascii; 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:03:32 -0000 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 -- Guido Falsi