Date: Thu, 23 Apr 2015 00:36:59 +0000 From: bugzilla-noreply@freebsd.org To: freebsd-ports-bugs@FreeBSD.org Subject: [Bug 199633] graphics/jpeg-turbo: includes should be installed, rework proposed Message-ID: <bug-199633-13@https.bugs.freebsd.org/bugzilla/>
next in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=199633 Bug ID: 199633 Summary: graphics/jpeg-turbo: includes should be installed, rework proposed Product: Ports & Packages Version: Latest Hardware: Any OS: Any Status: New Severity: Affects Many People Priority: --- Component: Individual Port(s) Assignee: freebsd-ports-bugs@FreeBSD.org Reporter: amdmi3@FreeBSD.org CC: bytestore@yandex.ru Flags: maintainer-feedback?(bytestore@yandex.ru) CC: bytestore@yandex.ru I have a new port which explicitly requires libjpeg-turbo, including its headers (it uses stuff not present in headers of graphics/jpeg). Currently the headers are not installed. The primary purpose of this PR is to add headers installation - this may be done by simply moving them into dedicated directory (e.g. include/jpeg-turbo). However I also propose ravamp of jpeg-turbo ports as the way they are split is seemingly meaningless, confusing and hard to use. I propose to merge these into a single port which installs all parts of jpeg-turbo in a way to not conflict with graphics/jpeg: - lib/libturbojpeg.{a,so,so.*} - include/turbojpeg.h - lib/libjpeg-turbo.{a,so,so.*} - include/{jconfig,jerror,jmorecfg,jpeglib}-turbo.h - binaries and manpages This way - jpeg-turbo's own interface (libturbojpeg, turbojpeg.h) may be used as-is - jpeg-compatible interface may be used by patching consumers - separate port which just installs libmap.d entry may be added to use by ones who want to transparently use libjpeg-turbo library instead of one from graphics/jpeg. Note that I deliberately use filename suffixes for graphics/jpeg conflicting library and headers. We could use dedicated subdirectories and leave filenames unmodified (e.g. include/jpeg-turbo/{jconfig,jerror,jmorecfg,jpeglib}.h, lib/jpeg-turbo/libjpeg.{a,so,so.*}), however it's hard to handle as include/link paths come from many places and consumers may end up using graphics/jpeg stuff while they've wanted turbo. -- You are receiving this mail because: You are the assignee for the bug.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-199633-13>