On Nov 27, 2013, at 06:25, strom...@macports.org wrote: > Revision > 114014 > Author > strom...@macports.org > Date > 2013-11-27 04:25:38 -0800 (Wed, 27 Nov 2013) > Log Message > > py-pil: fix compiling with freetype > Modified Paths > > • trunk/dports/python/py-pil/Portfile > Added Paths > > • trunk/dports/python/py-pil/files/patch-_imagingft.c.diff > Diff > > Modified: trunk/dports/python/py-pil/Portfile (114013 => 114014) > > --- trunk/dports/python/py-pil/Portfile 2013-11-27 11:56:10 UTC (rev > 114013) > +++ trunk/dports/python/py-pil/Portfile 2013-11-27 12:25:38 UTC (rev > 114014) > > @@ -5,7 +5,7 @@ > > > > name py-pil > > version 1.1.7 > > -revision 6 > > +revision 7
The revision should only be increased if this changes the files that get installed. libLASi for example installed .h files containing the buggy freetype inclusion, which caused other software such as graphviz which uses libLASi to fail to build, so I had to increase the revision so that the fixed .h files get installed. > Added: trunk/dports/python/py-pil/files/patch-_imagingft.c.diff (0 => 114014) Here the problem seems to only to be in a .c file, which will be compiled, but does not itself get installed. _______________________________________________ macports-dev mailing list macports-dev@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-dev
