summaryrefslogtreecommitdiff
path: root/devel/zlib
AgeCommit message (Collapse)AuthorFilesLines
2005-02-23Add RMD160 digests.agc1-1/+2
2004-11-04Changes 1.2.2:adam4-38/+7
* Eliminate a potential security vulnerability when decoding invalid compressed data * Fix bug when decompressing dynamic blocks with no distance codes * Do not return error when using gzread() on an empty file
2004-10-03Libtool fix for PR pkg/26633, and other issues. Update libtool to 1.5.10tv2-4/+4
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.
2004-09-22Mechanical changes to package PLISTs to make use of LIBTOOLIZE_PLIST.jlam1-5/+1
All library names listed by *.la files no longer need to be listed in the PLIST, e.g., instead of: lib/libfoo.a lib/libfoo.la lib/libfoo.so lib/libfoo.so.0 lib/libfoo.so.0.1 one simply needs: lib/libfoo.la and bsd.pkg.mk will automatically ensure that the additional library names are listed in the installed package +CONTENTS file. Also make LIBTOOLIZE_PLIST default to "yes".
2004-08-31Added two patches for fixing possible security issue.reed5-4/+35
The CVS security ID is CAN-2004-0797. The fix is same as used by OpenBSD, Debian and Gentoo. (Didn't see any reference to issue on zlib webpages.) The OpenBSD announcement "zlib reliabilty fix" says: "could allow an attacker to crash programs linked with it." And the Gentoo announcement says "zlib contains a bug in the handling of errors in the inflate() and inflateBack() functions. ... An attacker could exploit this vulnerability to launch a Denial of Service attack on any application using the zlib library." PKGREVISION is bumped and BUILDLINK_RECOMMENDED.zlib added to buildlink3.mk file.
2004-07-06Unused.wiz1-121/+0
2004-05-26Use CFLAGS when creating the archive. This fixes building under IRIX64jschauma2-9/+9
using gcc, as we need the ABI specific flags.
2004-05-08nb1: install shlib as executable.tv3-5/+6
2004-03-29Match the template builtin.mk file in bsd.builtin.mk, and make the twojlam1-9/+9
packages that use builtin.mk files (graphics/xpm and pkgtools/x11-links) use the new format correctly.
2004-03-23USE_BUILDLINK3 must be set to "yes" or "no", not defined/undefined.jlam1-2/+2
2004-03-12Obey CPPFLAGS.tv2-4/+4
2004-03-10Split out the code that deals with checking whether the software isjlam2-103/+88
built-in or not into a separate builtin.mk file. The code to deal checking for built-in software is much simpler to deal with in pkgsrc. The buildlink3.mk file for a package will be of the usual format regardless of the package, which makes it simpler for packagers to update a package. The builtin.mk file for a package must define a single yes/no variable USE_BUILTIN.<pkg> that is used by bsd.buildlink3.mk to decide whether to use the built-in software or to use the pkgsrc software.
2004-02-18Reorder some lines so that BUILDLINK_USE_BUILTIN.<pkg> set in thejlam1-19/+21
environment overrides all other settings.
2004-02-12Create a new variable PREFER_NATIVE that has the opposite semanticsjlam2-6/+26
as PREFER_PKGSRC. Preferences are determined by the most specific instance of the package in either PREFER_PKGSRC or PREFER_NATIVE. If a package is specified in neither or in both variables, then PREFER_PKGSRC has precedence over PREFER_NATIVE.
2004-02-12Reorganize code so that any dependencies are checked as part of decidingjlam2-57/+52
whether the software is built-in or not. This facilitates implementing the forthcoming PKGSRC_NATIVE variable.
2004-02-06If we're passing through MAKEFLAGS variables whose values may containjlam2-4/+4
spaces, use the :Q modifier instead of double-quoting the value. This avoids breakage when executing the just-in-time su targets.
2004-02-05Make PREFER_PKGSRC just yes/no or a list of packages. This makes itjlam2-10/+6
simpler to understand.
2004-02-05Rename BUILDLINK_PREFER_PKGSRC to PREFER_PKGSRC so that we can use itsjlam2-10/+8
value outside of buildlink-related files.
2004-02-05Support a new global variable:jlam2-2/+18
BUILDLINK_PREFER_PKGSRC This variable determines whether or not to prefer the pkgsrc versions of software that is also present in the base system. This variable is multi-state: defined, or "yes" always prefer the pkgsrc versions not defined, or "no" only use the pkgsrc versions if needed by dependency requirements This can also take a list of packages for which to prefer the pkgsrc-installed software. The package names may be found by consulting the value added to BUILDLINK_PACKAGES in the buildlink[23].mk files for that package.
2004-01-26revert last - the problem has been fixed in bsd.buildlink3.mk.grant1-2/+2
2004-01-25if we have determined that we need pkgsrc zlib, setgrant1-2/+2
BUILDLINK_DEPENDS.zlib instead of adding to it. fixes a problem where a buildlink dependency would be added on both zlib>=1.1.4nb1 and zlib>=1.2.1, resulting in various buildlink breakage.
2004-01-24Support BUILDLINK_DEPENDS.<pkg> being a list of values.jlam1-5/+9
2004-01-19Fix brokenness introduced as part of the update of zlib to 1.2.1. Thejlam2-47/+109
updated package update bumped the zlib shared lib major, which required that BUILDLINK_DEPENDS.zlib be bumped as well. Rather then requiring zlib>=1.2.1 for packages that can use the built-in zlib on *BSD systems, allow those built-in versions to satisfy zlib>=1.1.4nb1 dependencies, and only require the latest version if no suitable zlib is found.
2004-01-13Create the man/man3 directory, so that this can be installed properly withjmmv1-2/+2
pkgviews. Closes PR pkg/24081 by Min Sik Kim.
2004-01-12Changes 1.2.1:adam8-204/+56
* inflate is about 20% faster and minimizes memory allocation * crc32 is about 50% faster * new functions and functionality * more supported architectures
2004-01-05bl3ifyjlam1-12/+5
2004-01-05Use S/+$// instead of C/\+$// to save a backslash. Very highlyjlam1-2/+2
recommended by seb :)
2004-01-05Sow BUILDLINK_USE_BUILTIN.<pkg> and reap _NEED_<PKG> variables.jlam1-21/+15
2004-01-04Re-arrange to match example buildlink3.mk file in bsd.buildlink3.mk.jlam1-4/+4
2004-01-03Initial sprinkling of work-in-progress buildlink3.mk files for using thejlam1-0/+72
buildlink3 framework.
2003-07-17s/netbsd.org/NetBSD.org/grant1-2/+2
2003-06-02Use tech-pkg@ in favor of packages@ as MAINTAINER for orphaned packages.jschauma1-2/+2
Should anybody feel like they could be the maintainer for any of thewe packages, please adjust.
2003-03-05Oops, restore NOT_FOR_PLATFORM (commented for my local testing).salo1-2/+2
2003-03-05Added fix for CAN-2003-0107 -salo6-5/+120
Buffer overflow in the gzprintf function in zlib 1.1.4, when zlib is compiled without vsnprintf or when long inputs are truncated using vsnprintf, allows attackers to cause a denial of service or possibly execute arbitrary code. From OpenBSD. Restore configure target and add check for [v]snprintf. Bump PKGREVISION.
2003-02-28mark Linux zlib as incompatible to avoid using base zlib which cangrant1-1/+4
cause problems with pkgsrc libtool, eg. libtool: link: AGE `4' is greater than the current interface number `1' libtool: link: `1:1:4' is not valid version information libtool: install: `libz.la' is not a valid libtool archive
2003-02-28s/LIBTOOL_VERSION/LIBTOOL_REQD/ to register correct dependency.grant1-2/+2
2003-02-16Darwin has no static libz, mark it incompatible.grant1-1/+4
2003-02-04Create a fake libtool archive so that libtool doesn't get confused sincejlam1-6/+14
libz.so exists in the base system, but the package creates a libz.la.
2002-12-23IRIX has an old zlib version, so make it use pkgsrc's zlib.jschauma1-1/+4
2002-10-10Unused.wiz1-67/+0
2002-09-01Mirror the libtool setup in bsd.pkg.mk since we can't use USE_LIBTOOL.jlam1-4/+5
2002-08-25Merge changes in packages from the buildlink2 branch that havejlam3-4/+65
buildlink2.mk files back into the main trunk. This provides sufficient buildlink2 infrastructure to start merging other packages from the buildlink2 branch that have already been converted to use the buildlink2 framework.
2002-08-07Enable building this package on <1.4, and add INCOMPAT_ZLIB settings forwiz2-3/+10
NetBSD releases that need it. Closes pkg/14782.
2002-08-07Create new variables INCOMPAT_ZLIB, INCOMPAT_BZIP2, INCOMPAT_READLINE,jlam1-3/+17
INCOMPAT_GETTEXT that are analogous to INCOMPAT_ICONV and contain lists of shell wildcards intended to match against ${MACHINE_PLATFORM}. These variables are used to note those platforms that have the named packages in the base system but are incompatible in some way from the pkgsrc version of the same package. Change INCOMPAT_CURSES to have the same sematics as above. These variables allow much greater precision in specifying which platforms have broken (for the purposes of pkgsrc) versions of software in the base system that must be ignored. The buildlink.mk files for these packages define private _INCOMPAT_* versions of these variables, and they contain the default lists of platforms that are known to have incompatible software bits. This addresses pkg/17775 submitted by Julien T. Letessier <julien.letessier at sun dot com>.
2002-03-12Update to 1.1.4, and update MASTER_SITES.wiz2-6/+9
Changes since 1.1.3: - ZFREE was repeated on same allocation on some error conditions. This creates a security problem described in http://www.zlib.org/advisory-2002-03-11.txt - Returned incorrect error (Z_MEM_ERROR) on some invalid data - Avoid accesses before window for invalid distances with inflate window less than 32K. - force windowBits > 8 to avoid a bug in the encoder for a window size of 256 bytes. (A complete fix will be available in 1.1.5).
2001-11-29Change ONLY_FOR_PLATFORM...SunOS to NOT_FOR_PLATFORM...NetBSDabs1-2/+2
This package works fine under RedHat 5.0 (I'm still trying to work out what karma I broke in order to be in a position to know this...)
2001-11-01Move pkg/ files into package's toplevel directoryzuntum2-1/+1
2001-09-10Homepage changedhubertf1-2/+2
2001-07-27Add dir_DEFAULT setting used by EVAL_PREFIX logic to set the defaultjlam1-1/+2
installation directory in case the package isn't installed.
2001-07-20Mechanical changes to buildlink.mk files to use EVAL_PREFIX to setjlam1-2/+2
BUILDLINK_PREFIX.<pkgname>. This allows buildlink to find X11BASE packages regardless of whether they were installed before or after xpkgwedge was installed. Idea by Alistair Crooks <agc@pkgsrc.org>.
generated by cgit v1.2.3 (git 2.39.1) at 2024-07-27 12:47:02 +0000