From owner-freebsd-ports@FreeBSD.ORG Fri Oct 3 09:08:26 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.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 4115814A for ; Fri, 3 Oct 2014 09:08:26 +0000 (UTC) Received: from mout.gmx.net (mout.gmx.net [212.227.17.22]) (using TLSv1.2 with cipher DHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mout.gmx.net", Issuer "TeleSec ServerPass DE-1" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id B6414D9F for ; Fri, 3 Oct 2014 09:08:25 +0000 (UTC) Received: from walrus.pepperland ([81.217.76.60]) by mail.gmx.com (mrgmx102) with ESMTPSA (Nemesis) id 0MBq8p-1XPlQh0m9v-00ArBj; Fri, 03 Oct 2014 11:08:12 +0200 Message-ID: <542E677A.7080205@gmx.net> Date: Fri, 03 Oct 2014 11:08:10 +0200 From: Stefan Ehmann User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:31.0) Gecko/20100101 Thunderbird/31.1.2 MIME-Version: 1.0 To: freebsd-ports@freebsd.org Subject: py-imaging vs. py-pillow Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit X-Provags-ID: V03:K0:dCyyq/edqOrZgo10+z8JGsc2HkaILK2TbmOUwLarAZr+ihM2ZUh Znbq3ULAs+UQ9w5gPm9ZgEcvo97vVk2yFjSB0IwpcTcFbPR8hVTqMYlBwTmIiz0VnXkh4TJ /b9Ev3dAhjIH60VmopL31Q3U+9gJ/9EnSZvE2796FjNgmqgkxjvKucbAOGt/pHHUeP5XiFH xEMDYMvx0G/1ktCtlxf8w== X-UI-Out-Filterresults: notjunk:1; Cc: koobs@FreeBSD.org, mainland@apeiron.net X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 03 Oct 2014 09:08:26 -0000 According to freshports there are about 10 ports that depend on py-pilllow and 50 that depend on py-imaging. py-imaging conflicts with py-pilllow. E.g., calibre and xmbc cannot be installed at the same time. I noticed the problem because calibre switched to py-pilllow recently. There really should be a way that these packages can coexist. (py-imaging/py-pilllow maintainers CCed)