Up to [NetBSD + pkgsrc-wip] / pkgsrc / graphics / tiff
Request diff between arbitrary revisions - Display revisions graphically
Keyword substitution: kv
Default branch: MAIN
-pull in xz/bl3 to avoid hidden dependency -update to 4.0.1 -- this only adds symbol versioning support to ease transition from 3.x to 4.x; this is not used in pkgsrc so the update is purely cosmetical
Bump ABI depends, which was the whole cause of the PKGREVISION bump. Oops.
Mechanically replace references to graphics/jpeg with the suitable
alternative from mk/jpeg.buildlink3.mk
This allows selection of an alternative jpeg library (namely the x86 MMX,
SSE, SSE2 accelerated libjpeg-turbo) via JPEG_DEFAULT=libjpeg-turbo, and
follows the current standard model for alternatives (fam, motif, fuse etc).
The mechanical edits were applied via the following script:
#!/bin/sh
for d in */*; do
[ -d "$d" ] || continue
for i in "$d/"Makefile* "$d/"*.mk; do
case "$i" in *.orig|*"*"*) continue;; esac
out="$d/x"
sed -e 's;graphics/jpeg/buildlink3\.mk;mk/jpeg.buildlink3.mk;g' \
-e 's;BUILDLINK_PREFIX\.jpeg;JPEGBASE;g' \
< "$i" > "$out"
if cmp -s "$i" "$out"; then
rm -f "$out"
else
echo "Edited $i"
mv -f "$i" "$i.orig" && mv "$out" "$i"
fi
done
done
Second try at jpeg-8 recursive PKGREVISION bump.
bump revision because of graphics/jpeg update
Simply and speed up buildlink3.mk files and processing. This changes the buildlink3.mk files to use an include guard for the recursive include. The use of BUILDLINK_DEPTH, BUILDLINK_DEPENDS, BUILDLINK_PACKAGES and BUILDLINK_ORDER is handled by a single new variable BUILDLINK_TREE. Each buildlink3.mk file adds a pair of enter/exit marker, which can be used to reconstruct the tree and to determine first level includes. Avoiding := for large variables (BUILDLINK_ORDER) speeds up parse time as += has linear complexity. The include guard reduces system time by avoiding reading files over and over again. For complex packages this reduces both %user and %sys time to half of the former time.
Change the format of BUILDLINK_ORDER to contain depth information as well, and add a new helper target and script, "show-buildlink3", that outputs a listing of the buildlink3.mk files included as well as the depth at which they are included. For example, "make show-buildlink3" in fonts/Xft2 displays: zlib fontconfig iconv zlib freetype2 expat freetype2 Xrender renderproto
Track information in a new variable BUILDLINK_ORDER that informs us of the order in which buildlink3.mk files are (recursively) included by a package Makefile.
Over 1200 files touched but no revisions bumped :) RECOMMENDED is removed. It becomes ABI_DEPENDS. BUILDLINK_RECOMMENDED.foo becomes BUILDLINK_ABI_DEPENDS.foo. BUILDLINK_DEPENDS.foo becomes BUILDLINK_API_DEPENDS.foo. BUILDLINK_DEPENDS does not change. IGNORE_RECOMMENDED (which defaulted to "no") becomes USE_ABI_DEPENDS which defaults to "yes". Added to obsolete.mk checking for IGNORE_RECOMMENDED. I did not manually go through and fix any aesthetic tab/spacing issues. I have tested the above patch on DragonFly building and packaging subversion and pkglint and their many dependencies. I have also tested USE_ABI_DEPENDS=no on my NetBSD workstation (where I have used IGNORE_RECOMMENDED for a long time). I have been an active user of IGNORE_RECOMMENDED since it was available. As suggested, I removed the documentation sentences suggesting bumping for "security" issues. As discussed on tech-pkg. I will commit to revbump, pkglint, pkg_install, createbuildlink separately. Note that if you use wip, it will fail! I will commit to pkgsrc-wip later (within day).
Pullup ticket 495 - requested by Lubomir Sedlacik
security fix for tiff
Revisions pulled up:
- pkgsrc/graphics/tiff/Makefile 1.67, 1.69
- pkgsrc/graphics/tiff/PLIST 1.7
- pkgsrc/graphics/tiff/distinfo 1.26, 1.27, 1.28, 1.29
- pkgsrc/graphics/tiff/options.mk 1.1
- pkgsrc/graphics/tiff/buildlink3.mk 1.12
- pkgsrc/graphics/tiff/patches/patch-aa 1.16
- pkgsrc/graphics/tiff/patches/patch-ab 1.16
- pkgsrc/graphics/tiff/patches/patch-ac 1.16
- pkgsrc/graphics/tiff/patches/patch-ad 1.14
- pkgsrc/graphics/tiff/patches/patch-ae removed
- pkgsrc/graphics/tiff/patches/patch-af removed
- pkgsrc/graphics/tiff/patches/patch-ah removed
- pkgsrc/graphics/tiff/patches/patch-ag removed
Module Name: pkgsrc
Committed By: wiz
Date: Wed Mar 23 01:17:45 UTC 2005
Modified Files:
pkgsrc/graphics/tiff: Makefile PLIST distinfo
pkgsrc/graphics/tiff/patches: patch-aa
Added Files:
pkgsrc/graphics/tiff: options.mk
Removed Files:
pkgsrc/graphics/tiff/patches: patch-ab patch-ac patch-ad patch-ae
patch-af patch-ag patch-ah
Log Message:
Update to 3.7.2.
Package changes:
Put options in options.mk, and retire support for USE_GIF; turn on
the lzw option by default (since USE_GIF was on by default).
C++ library's name changed, to be in sync with tiff distribution's name
for it (libtiffcxx -> libtiffxx).
Changes in 3.7.2:
Maintainance [sic] release. Many bugfixes in the build
environment and compatibility improvements.
----
Module Name: pkgsrc
Committed By: recht
Date: Thu Mar 24 17:46:29 UTC 2005
Modified Files:
pkgsrc/graphics/tiff: distinfo
Added Files:
pkgsrc/graphics/tiff/patches: patch-ab
Log Message:
Pull in libtiff/Makefile.in rev. 1.54 and 1.55 without the rpath changes
from libtiff CVS to fix the build on Darwin.
----
Modified Files:
pkgsrc/graphics/tiff: distinfo
Added Files:
pkgsrc/graphics/tiff/patches: patch-ac
Log Message:
Fix for NetBSD LP64 arches by checking if _LP64 is defined. These arches
don't define __LP64__. This is basically same as patch-ab rev. 1.13,
which was probably removed by mistake.
----
Module Name: pkgsrc
Committed By: salo
Date: Thu May 12 12:53:21 UTC 2005
Modified Files:
pkgsrc/graphics/tiff: Makefile buildlink3.mk distinfo
Added Files:
pkgsrc/graphics/tiff/patches: patch-ad
Log Message:
Security fix:
"A vulnerability in libTIFF was found, it can be potentially exploited by
malicious people to compromise a vulnerable system."
http://secunia.com/advisories/15320/
http://bugzilla.remotesensing.org/show_bug.cgi?id=3D843
Bump PKGREVISION, patch from libtiff cvs repository.
Security fix: "A vulnerability in libTIFF was found, it can be potentially exploited by malicious people to compromise a vulnerable system." http://secunia.com/advisories/15320/ http://bugzilla.remotesensing.org/show_bug.cgi?id=843 Bump PKGREVISION, patch from libtiff cvs repository.
Create a separate libtiffcxx.so library for use by C++ applications. It's meant to be used directly in place of libtiff.so, i.e. instead of linking against -ltiff, you link against -ltiffcxx. It also leaves libtiff.so as a plain C-linkage library again, as it was in tiff-3.6.x, and avoids needing to patch tiff-using packages to link using the C++ compiler. Bump the PKGREVISION to 1.
Upgrade tiff to 3.7.1. Remove OpenWindows workaround in pkgsrc for this. Too many changes to include here. See http://www.remotesensing.org/libtiff/v3.7.1.html and http://www.remotesensing.org/libtiff/v3.7.0.html and previous change files for changes information. tiff-3.7.1 now includes the lzw compression code again. It also uses autoconf and libtool now. A new tool is bmp2tiff. Docs are placed under share/doc/tiff/html instead of share/doc/html/tiff. Many manpage symlinks are now missing. (This was reported to tiff list.)
Pullup ticket 174 - requested by Jeremy C. Reed
security fix for tiff
Module Name: pkgsrc
Committed By: reed
Date: Wed Dec 22 03:57:15 UTC 2004
Modified Files:
pkgsrc/graphics/tiff: Makefile buildlink3.mk distinfo
pkgsrc/graphics/tiff/patches: patch-ag patch-ao
Log Message:
patch-ag and patch-ao already had security fixes for CESA-2004-006.
But now these are improved in response to
iDEFENSE Security Advisory 12.21.04
www.idefense.com/application/poi/display?id=173&type=vulnerabilities
libtiff STRIPOFFSETS Integer Overflow Vulnerability
December 21, 2004
This fix (in two files) was from that advisory and also seen
in tiff 3.7.1.
PKGREVISION is bumped to 6 and BUILDLINK_RECOMMENDED is adjusted for
this possible security issue. Other packages depending on this are not
bumped.
patch-ag and patch-ao already had security fixes for CESA-2004-006. But now these are improved in response to iDEFENSE Security Advisory 12.21.04 www.idefense.com/application/poi/display?id=173&type=vulnerabilities libtiff STRIPOFFSETS Integer Overflow Vulnerability December 21, 2004 This fix (in two files) was from that advisory and also seen in tiff 3.7.1. PKGREVISION is bumped to 6 and BUILDLINK_RECOMMENDED is adjusted for this possible security issue. Other packages depending on this are not bumped.
Libtool fix for PR pkg/26633, and other issues. Update libtool to 1.5.10 in the process. (More information on tech-pkg.) Bump PKGREVISION and BUILDLINK_DEPENDS of all packages using libtool and installing .la files. Bump PKGREVISION (only) of all packages depending directly on the above via a buildlink3 include.
Fix serious bug where BUILDLINK_PACKAGES wasn't being ordered properly by moving the inclusion of buildlink3.mk files outside of the protected region. This bug would be seen by users that have set PREFER_PKGSRC or PREFER_NATIVE to non-default values. BUILDLINK_PACKAGES should be ordered so that for any package in the list, that package doesn't depend on any packages to the left of it in the list. This ordering property is used to check for builtin packages in the correct order. The problem was that including a buildlink3.mk file for <pkg> correctly ensured that <pkg> was removed from BUILDLINK_PACKAGES and appended to the end. However, since the inclusion of any other buildlink3.mk files within that buildlink3.mk was in a region that was protected against multiple inclusion, those dependencies weren't also moved to the end of BUILDLINK_PACKAGES.
Reorder location and setting of BUILDLINK_PACKAGES to match template buildlink3.mk file in revision 1.101 of bsd.buildlink3.mk.
The BUILDLINK_DEPENDS.<pkg> lines should match between the buildlink3.mk and any pre-existing buildlink2.mk files.
Append to BUILDLINK_DEPENDS.<pkg> instead of setting a default value. In the normal case when BUILDLINK_DEPENDS.<pkg> isn't specified, it receives a value only once due to the multiple inclusion protection in the bulldlink3.mk files. In the case where a package includes several buildlink3.mk files that each want a slightly different version of another dependency, having BUILDLINK_DEPENDS.<pkg> be a list allows for the strictest <pkg> dependency to be matched.
Use S/+$// instead of C/\+$// to save a backslash. Very highly recommended by seb :)
Re-arrange to match example buildlink3.mk file in bsd.buildlink3.mk.
Initial sprinkling of work-in-progress buildlink3.mk files for using the buildlink3 framework.