| Age | Commit message (Collapse) | Author | Files | Lines |
|---|
|
USE_GNU_TOOLS -> USE_TOOLS
awk -> gawk
m4 -> gm4
make -> gmake
sed -> gsed
yacc -> bison
|
|
PR pkg/29883.
|
|
|
|
|
|
tech-pkg@.
|
|
Some BUILDLINK_RECOMMENDED bumps done also.
(If I missed any, please let me know -- and let me know a good
way to automate this.)
|
|
Suggested by Roland Illig, ok'd by various.
|
|
|
|
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.
|
|
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".
|
|
|
|
a working sed.
Addresses PR pkg/25306 by Georg Schwarz.
|
|
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.
|
|
buildlink3.mk file in revision 1.101 of bsd.buildlink3.mk.
|
|
relative to ${WRKSRC}. Remove redundant LIBTOOL_OVERRIDE settings that
are automatically handled by the default setting in bsd.pkg.mk.
|
|
existing value. This is critical to set the correct list of dependencies
for a package.
|
|
|
|
|
|
Tiff is backward compatible, but was broken on amd64 platform
so this makes sure new tiff is used.
|
|
|
|
|
|
(Forgot the last time we did this. Pointed out by Sergey
Svishchev (svs at ropnet dot ru))
|
|
|
|
|
|
include several buildlink2.mk files.
|
|
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.
|
|
|
|
PDFlib 4.0.3 is a free maintenance release for all customers with a 4.x
license. Your previous license key will work with this update, too. A
detailed account of changes since PDFlib 4.0.0 is available in the change log
at http://www.pdflib.com/pdflib/changes4.txt.
|
|
all dependencies on packages depending on "png" which contain shared
libraries, all for the (imminent) update to the "png" package.
[List courtesy of John Darrow, courtesy of "bulk-build".]
|
|
|
|
differs from the distfile version number. G/C some the unused variables
in pdflib/Makefile.common related to the old way of handling version
numbers. Invent PDFLIB_BASE_VERS, which is ${PDFLIB_DIST_VERS} that's
been munged so that's understandable by the pkg_* tools' wildcard version
numbering logic.
|
|
|
|
we can remove REPLACE_BUILDLINK settings containing *-config, *Conf.sh, and
*.pc.
|
|
installed files. We don't want buildlink references to escape into the
install directory.
|
|
language bindings for PDFlib: we split the Makefile in a common part and
a package-specific part, and we cause the configure script to substitute
the correct values to link against an installed libpdf.so when linking
the binding shared objects.
|
|
set FOO_CONFIG=${BUILDLINK_CONFIG_WRAPPER.foo} in both CONFIGURE_ENV and
MAKE_ENV. We remove the check for GNU_CONFIGURE because if a package
Makefile includes the buildlink.mk file, then it most likely wants to use
the config script wrappers as well. Change suggested by Hubert Feyrer
(hubertf) and Tomasz Luchowski (zuntum).
|
|
|
|
optimizations, bug fixes in image-handling for JPEG, TIFF and PNG files,
support for TrueType fonts, and pluggin some memory leaks. The API changed
slightly and a major number bump on the shared library occurred.
Convert to use buildlink.mk files and mark as USE_BUILDLINK_ONLY. Add a
buildlink.mk file for use by other package Makefiles. Also install the
license info and PDFlib manual.
|
|
Noted by Frederick Bruckman.
|
|
sizes.
|
|
+ move the patch digest/checksum values from files/patch-sum to distinfo
|
|
using the newest PNG library won't work on system with an older one. To
prevent such problems with precompiled binary packages require at least
"png-1.0.9nb1" in all dependences.
|
|
|
|
Changes:
Fixes bugs related to text positioning and text box formatting
Fixes bugs in the graphics engine, mostly related to arc drawing and subpath handling
Fixes an ActiveX crash in the open_image() function.
Improves internal accuracy and output accuracy of floating point numbers for better positioning
Fine-tunes UPR and encoding handling
Allows the base 14 fonts to be embedded
Makes TIFF and JPEG handling more robust against bad files.
Detects more illegal function call sequences
Makes exceptions thrown by the font machinery configurable in favor of error return values
Many improvements for using PDFlib on IBM S/390 (iServer zSeries), including fixes for several crashes, and an EBCDIC-safe Java wrapper (binaries available soon)
Introduces a dedicated PDFlib distribution for EBCDIC systems
Adds more documentation on using the language bindings in diverse environments, e.g. Java application servers
Splits the manual in two editions: one for the PDFlib ActiveX edition, and one for the other language bindings.
Adds more examples and algorithms to the PDFlib manual
Adds examples and documentation for using PDFlib with Allaire ColdFusion
Introduces support for querying several of the existing PDFlib parameters
|
|
out of date - it was based on a.out OBJECT_FMT, and added entries in the
generated PLISTs to reflect the symlinks that ELF packages uses. It also
tried to be clever, and removed and recreated any symbolic links that were
created, which has resulted in some fun, especially with packages which
use dlopen(3) to load modules. Some recent changes to our ld.so to bring
it more into line with other Operating Systems also exposed some cracks.
+ Modify bsd.pkg.mk and its shared object handling, so that PLISTs now contain
the ELF symlinks.
+ Don't mess about with file system entries when handling shared objects in
bsd.pkg.mk, since it's likely that libtool and the BSD *.mk processing will
have got it right, and have a much better idea than we do.
+ Modify PLISTs to contain "ELF symlinks"
+ On a.out platforms, delete any "ELF symlinks" from the generated PLISTs
+ On ELF platforms, no extra processing needs to be done in bsd.pkg.mk
+ Modify print-PLIST target in bsd.pkg.mk to add dummy symlink entries on
a.out platforms
+ Update the documentation in Packages.txt
With many thanks to Thomas Klausner for keeping me honest with this.
|
|
|
|
Add a new USE_LIBTOOL definition that uses the libtool package instead of
pkglibtool which is now considered outdated.
USE_PKGLIBTOOL is available for backwards compatibility with old packages
but is deprecated for new packages.
|
|
too many changes since 2.01 to list here, the most visible for me is that it
is libtoolized - see doc/changes.txt for the rest
|
|
|
|
environment, bugfixes and documentation improvements.
|
