Skip site navigation (1)Skip section navigation (2)
Date:      Fri, 03 Oct 2014 14:01:32 +0200
From:      Stefan Ehmann <shoesoft@gmx.net>
To:        William Grzybowski <wg@freebsd.org>
Cc:        koobs@freebsd.org, mainland@apeiron.net, "freebsd-ports@freebsd.org" <freebsd-ports@freebsd.org>
Subject:   Re: py-imaging vs. py-pillow
Message-ID:  <542E901C.9060203@gmx.net>
In-Reply-To: <CAHtVNLNs_tm8cg6xu3N_DAQ8O=LPk3VOH_sAVp-nJgwQBniFkQ@mail.gmail.com>
References:  <542E677A.7080205@gmx.net> <CAHtVNLNs_tm8cg6xu3N_DAQ8O=LPk3VOH_sAVp-nJgwQBniFkQ@mail.gmail.com>

next in thread | previous in thread | raw e-mail | index | archive | help
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.



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?542E901C.9060203>