RFC: Mk/bsd.jpeg.mk to automagically handle jpeg dependency

Scot Hetzel swhetzel at gmail.com
Wed Jun 16 15:35:58 UTC 2010

On Wed, Jun 16, 2010 at 3:56 AM, Peter Pentchev <roam at ringlet.net> wrote:
> On Tue, Jun 15, 2010 at 10:09:57PM -0300, Mario Sergio Fujikawa Ferreira wrote:
>>       It will automagically detected the already installed jpeg
>> port variant (libjpeg-turbo or jpeg) and depend on it. If the user prefers to set the variant, he can do so using
>> WITH_JPEG=    jpeg
>> or
>> WITH_JPEG=    libjpeg-turbo
> Is it possible that this will conflict with ports that have a JPEG item
> in their OPTIONS list?  There are at least the astro/xplanet, editors/emacs,
> graphics/devil, graphics/gdal, graphics/gegl, graphics/grx, graphics/imlib2,
> graphics/ocaml-images, graphics/opencv, graphics/podofo, graphics/tumbler,
> mail/spamprobe, math/R, multimedia/gmerlin, multimedia/gpac-libgpac,
> multimedia/libquicktime, multimedia/spook, multimedia/transcode, x11/aterm,
> x11-fm/thunar, x11/mrxvt-devel, and x11-wm/jwm ports that do that, and
> there might be more that a simple fgrep -le WITH_JPEG -e WITHOUT_JPEG did
> not catch.
Since many ports use JPEG as an item in their OPTIONS list to enable
jpeg support in the port, why not use WITH_JPEG_PORT to allow the
administrator to choose which jpeg port to depend on.


More information about the freebsd-ports mailing list