From owner-freebsd-ports@FreeBSD.ORG Fri Oct 3 12:01:39 2014 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id BD0F4F82; Fri, 3 Oct 2014 12:01:39 +0000 (UTC) Received: from mout.gmx.net (mout.gmx.net [212.227.17.20]) (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 54375189; Fri, 3 Oct 2014 12:01:39 +0000 (UTC) Received: from walrus.pepperland ([81.217.76.60]) by mail.gmx.com (mrgmx102) with ESMTPSA (Nemesis) id 0M2nfO-1YP6pn44v8-00sbwZ; Fri, 03 Oct 2014 14:01:34 +0200 Message-ID: <542E901C.9060203@gmx.net> Date: Fri, 03 Oct 2014 14:01:32 +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: William Grzybowski Subject: Re: py-imaging vs. py-pillow References: <542E677A.7080205@gmx.net> In-Reply-To: Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit X-Provags-ID: V03:K0:C+cbk0aSNwNAO1pwsHRA2ToLlFR8kafpFVqF/72hYDxDcMKFUzW tmdmGWhC3xwT5Nza2xYn15mk9ZVrA6xfMpIZmJcgZlklb0PNXwcwg0raVZnadzsbFIRQHVL SS/7S4de3Lc5YRSm74vZOgOKa/K/JcM5YWclMnuwtJgQWOZd69La/zqLgnolWZGqlvZzEWr nNQk1Ws8wPA0owUxXdCHQ== X-UI-Out-Filterresults: notjunk:1; Cc: koobs@freebsd.org, mainland@apeiron.net, "freebsd-ports@freebsd.org" 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 12:01:39 -0000 On 03.10.2014 13:37, William Grzybowski wrote: > Coexist how? They are essentially the same package. I don't see how > thats possible. I meant that you should be able to install ports that depend on py-imaging and ports that depend on py-imaging at the same time. > py-imaging is deprecated, they should be switched to py-pillow and thats it. If py-pillow is a compatible drop-in replacement of py-imaging then that's probably the best solution.