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).
Several changes are involved since they are all interrelated. These
changes affect about 1000 files.
The first major change is rewriting bsd.builtin.mk as well as all of
the builtin.mk files to follow the new example in bsd.builtin.mk.
The loop to include all of the builtin.mk files needed by the package
is moved from bsd.builtin.mk and into bsd.buildlink3.mk. bsd.builtin.mk
is now included by each of the individual builtin.mk files and provides
some common logic for all of the builtin.mk files. Currently, this
includes the computation for whether the native or pkgsrc version of
the package is preferred. This causes USE_BUILTIN.* to be correctly
set when one builtin.mk file includes another.
The second major change is teach the builtin.mk files to consider
files under ${LOCALBASE} to be from pkgsrc-controlled packages. Most
of the builtin.mk files test for the presence of built-in software by
checking for the existence of certain files, e.g. <pthread.h>, and we
now assume that if that file is under ${LOCALBASE}, then it must be
from pkgsrc. This modification is a nod toward LOCALBASE=/usr. The
exceptions to this new check are the X11 distribution packages, which
are handled specially as noted below.
The third major change is providing builtin.mk and version.mk files
for each of the X11 distribution packages in pkgsrc. The builtin.mk
file can detect whether the native X11 distribution is the same as
the one provided by pkgsrc, and the version.mk file computes the
version of the X11 distribution package, whether it's built-in or not.
The fourth major change is that the buildlink3.mk files for X11 packages
that install parts which are part of X11 distribution packages, e.g.
Xpm, Xcursor, etc., now use imake to query the X11 distribution for
whether the software is already provided by the X11 distribution.
This is more accurate than grepping for a symbol name in the imake
config files. Using imake required sprinkling various builtin-imake.mk
helper files into pkgsrc directories. These files are used as input
to imake since imake can't use stdin for that purpose.
The fifth major change is in how packages note that they use X11.
Instead of setting USE_X11, package Makefiles should now include
x11.buildlink3.mk instead. This causes the X11 package buildlink3
and builtin logic to be executed at the correct place for buildlink3.mk
and builtin.mk files that previously set USE_X11, and fixes packages
that relied on buildlink3.mk files to implicitly note that X11 is
needed. Package buildlink3.mk should also include x11.buildlink3.mk
when linking against the package libraries requires also linking
against the X11 libraries. Where it was obvious, redundant inclusions
of x11.buildlink3.mk have been removed.
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".
Changes since 2.3.15:
art_render_gradient.c: revert the double comparison test in the
asserts and comment out the two asserts causing crashes
everywhere.
2003-08-08 Alexander Larsson <alexl@redhat.com>
* configure.in: 2.3.14
Fri Jul 25 12:29:35 2003 George Lebl <jirka@5z.com>
* art_render_gradient.c (art_render_gradient_linear_render_8)
(art_render_gradient_linear_render) (art_render_gradient_linear)
(art_render_gradient_radial_render) (art_render_gradient_radial):
Redo the checks where float was compared by == or != to using
the EPSILON define. Also copy the ArtGradientLinear and
ArtGradientRadial into the source structure, pretending that
these are constants that will never change or be freed by
the caller is utterly evil and in fact for librsvg it is
not constant. This fixes some more very random crashes
when using librsvg with libart (which seems to be the
only usage of the gradient stuff)
Fri Jul 18 12:57:36 2003 George Lebl <jirka@5z.com>
* art_render_gradient.c: Fix more comparison-of-doubles by == bugs,
this code is uber ugly. Should fix the fairly random crashes
on asserts I've been having.
2003-07-11 Michael Meeks <michael@ximian.com>
* Version 2.3.13
2003-07-11 Federico Mena Quintero <federico@ximian.com>
* art_svp_ops.c (art_svp_minus): impl.
Tue Jul 08 01:15:02 2003 George Lebl <jirka@5z.com>
* art_render_gradient.c: fix comment as pointed out by alex
Tue Jul 08 01:13:48 2003 George Lebl <jirka@5z.com>
* art_render_gradient.c (art_render_gradient_linear_render_8):
when we wish to find the current segment and we go beyond the
last stop due to float fun, use the last segment as that's
really what we want. Avoids a very abrupt assert death.
2003-05-05 Alexander Larsson <alexl@redhat.com>
* configure.in:
Bump to 2.3.12
2003-04-24 Alexander Larsson <alexl@redhat.com>
* art_uta_vpath.c (art_uta_from_vpath):
Don't silently stomp on memory on bad vpaths.
2003-04-11 Alexander Larsson <alexl@redhat.com>
* art_svp_vpath_stroke.c (render_seg):
Handle cases when dmr2 is very small better.
2003-04-10 Alexander Larsson <alexl@redhat.com>
* art_svp_wind.c (x_order_2):
Handle horizontally aligned segments.
* art_render_svp.c (art_render_svp_callback,
art_render_svp_callback_span, art_render_svp_callback_opacity,
art_render_svp_callback_opacity_span): if no runs would
normally be emitted, but start is greater than zero, emit a
single run covering the entire width of the rendered region.
* autogen.sh: hardcode aclocal-1.4/automake-1.4 so that users with
both automake 1.6 and 1.4 installed get the right automake. Means
compilation from CVS will now require the latest automake 1.4
release, or manually creating symlinks called "automake-1.4" and
"aclocal-1.4".
into the NetBSD packages collection.
Provided in PR 16932 by jmmv@hispabsd.org (Julio Merino).
Libart is a library for high-performance 2D graphics. It is currently
being used as the antialiased rendering engine for the Gnome Canvas.
It is also the rendering engine for Gill, the Gnome Illustration app.
Libart supports a very powerful imaging model, basically the same as
SVG and the Java 2D API. It includes all PostScript imaging
operations, and adds antialiasing and alpha-transparency.
Libart is also highly tuned for incremental rendering. It contains
data structures and algorithms suited to rapid, precise computation
of Region of Interest, as well as a two-phase rendering pipeline
optimized for interactive display.
