py-imaging vs. py-pillow

[Kevin Oberman]

On Sat, Oct 11, 2014 at 6:08 AM, William Grzybowski <wg at freebsd.org> wrote:

> Should be fixed now, small typo in the option depends.
>
> Thanks.
>
> On Sat, Oct 11, 2014 at 9:59 AM, Beeblebrox <zaphod at berentweb.com> wrote:
> > Build fails if tiff is enabled (py27-pillow-2.6.0)
> >
> > OPTIONS_FILE_SET+=TIFF
> > Gives: "ValueError: --enable-tiff requested but tiff not found, aborting"
> >
> > Just advising in case you have not been made aware.
> > Regards.
> >
> >
> >
> >
> > -----
> > FreeBSD-11-current_amd64_root-on-zfs_RadeonKMS
> > --
> > View this message in context:
> http://freebsd.1045724.n5.nabble.com/py-imaging-vs-py-pillow-tp5954043p5955962.html
> > Sent from the freebsd-ports mailing list archive at Nabble.com.
> > _______________________________________________
> > freebsd-ports at freebsd.org mailing list
> > http://lists.freebsd.org/mailman/listinfo/freebsd-ports
> > To unsubscribe, send any mail to "freebsd-ports-unsubscribe at freebsd.org"
>
>
>
> --
> William Grzybowski / wg
> FreeBSD Ports Committer
> _______________________________________________
> freebsd-ports at freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-ports
> To unsubscribe, send any mail to "freebsd-ports-unsubscribe at freebsd.org"
>

print/hplip is still building with py-imaging and I had to delete it to get
py-opengl to update. I suspect that just changing "py-imaging" to
"py-pillow" in Makefile would do the trick.