New in 0.4.0:
* Real time timestamping support. (Dennis)
* Will unref plugins that don't match the ABI version. (Dennis)
* Added VisRectangle system. (Dennis)
* New BMP loader that supports all depths and RLE encoding. (Sepp)
* visual_mem_set(), visual_mem_set16(), visual_mem_set32()
Optimized memset functions. (Dennis)
* VisVideo new composite system. (Dennis)
* VisVideo sub regions. (Dennis)
* visual_video_zoom_*(). (Jaak)
* visual_video_mirror_*(). (Jaak)
* visual_video_rotate_*(). (Jaak)
* Removed obsolete visual_video_depth_transform_to_buffer(). (Jaak)
* Added VisCollection system. (Dennis)
* Added VisHashmap. (Dennis)
* Added VisCache. (Dennis)
* VisAudio rewrite. (Dennis)
* Added .license bit to VisPluginInfo for realtime license check. (Dennis)
* Removed .struct_size and .api_version from the VisPluginInfo structure,
and revamped the plugin version check system. Put
VISUAL_PLUGIN_API_VERSION_VALIDATOR somewhere in your plugin and it'll
work. (Dennis)
* Homedir installable plugins ~/.libvisual/actor transform morph input. (Dennis)
* Added VisOS. Realtime priority functions are hosted in this module. (Dennis)
* Added VisMath. All kind of math related functions have been added, most
note worthy are the _vectorized_. All of these are accelerated by
mmx/3dnow/sse instructions.
* VisFourier completely revamped. (Chong Kai Xiong)
Breaks compatibility with 0.2 releases.
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).
developer is officially maintaining the package.
The rationale for changing this from "tech-pkg" to "pkgsrc-users" is
that it implies that any user can try to maintain the package (by
submitting patches to the mailing list). Since the folks most likely
to care about the package are the folks that want to use it or are
already using it, this would leverage the energy of users who aren't
developers.
file's sole purpose was to provide a dependency on pkg-config and set
some environment variables. Instead, turn pkg-config into a "tool"
in the tools framework, where the pkg-config wrapper automatically
adds PKG_CONFIG_LIBDIR to the environment before invoking the real
pkg-config.
For all package Makefiles that included pkg-config/buildlink3.mk, remove
that inclusion and replace it with USE_TOOLS+=pkg-config.
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.
Libvisual is an abstraction library that comes between applications
and audio visualisation plugins.
Often when it comes to audio visualisation plugins or programs that
create visuals, they depend on a player or something else; basically,
there is no general framework that enabled application developers
to easily access cool audio visualisation plugins. Libvisual wants
to change this by providing an interface towards plugins and
applications; through this easy to use interface applications can
easily access plugins and, since the drawing is done by the
application, it also enables the developer to draw the visual
anywhere he wants.
The framework also allows you to morph to different plugins and
mix two at once; all kinds of neat tricks are possible using this
method.
