problem with the build on DragonFly:
/usr/libexec/binutils215/elf/ld: : No such file: No such file or directory
is not a very helpful message to trace down to a spurious comma.
I'm not sure how this built at all on other platforms.
Dasher 4.0.4
* Fixed error introduced in last commit
* Backported bugfix from HEAD
Dasher 4.0.3
* Fixed compile error when --without-gnome specified
* Regenerated configure to match configure.in
since they always need a C compiler, even when the source code is
completely in C++.
For some other packages, stated in the comment that a C compiler is
really not needed.
PKGLOCALEDIR and which install their locale files directly under
${PREFIX}/${PKGLOCALEDIR} and sort the PLIST file entries. From now
on, pkgsrc/mk/plist/plist-locale.awk will automatically handle
transforming the PLIST to refer to the correct locale directory.
=============
Dasher 4.0.0
=============
* Promoted to stable release
=============
Dasher 3.99.5
=============
* New icon
* Bugfixes in 'enter text into other windows' mode
=============
Dasher 3.99.4
=============
* Fixed font behaviour in Windows
* Fixed broken start/stop in dynamic button mode
* Other minor bugfixes
=============
Dasher 3.99.3
=============
* Bugfix to tarball
=============
Dasher 3.99.2
=============
* Improved button mode support
* Cairo support ported from 3.2 branch
* Win32 should build from tarball again
* Bugfixes
=============
Dasher 3.99.1
=============
New 4.0.0 preview, highlights include:
* (Partial) button mode support
* Infinite back off
* Improved symbol grouping in alphabets
* New status bar, with 'favourite' alphabet selection
=============
Dasher 3.99.0
=============
First preview of 4.0.0 - many changes and re-writes
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.
2005-01-30 Matthew Garrett <mjg59@srcf.ucam.org>
* Make autogen.sh do the right thing
* Add Bengali support (from sayamindu@gnome.org)
* Add a couple of colons to remove gcc warnings (from sobhi@us.ibm.com)
* Make sure non-void functions return something (from
clahey@ximian.com)
* Check in /usr/X11R6/lib64 for libXtst (from clahey@ximian.com)
* Fix up string length checking - avoid crashes when "Speak on stop"
switched on
* Version 3.2.13
2005-01-25 Matthew Garrett <mjg59@srcf.ucam.org>
* Fix a couple of crash bugs in the window-focus handling
* Make window choice available on non-accessible builds
2005-01-12 Matthew Garrett <mjg59@srcf.ucam.org>
* Make the build system work after autotools make my life miserable
again.
* Add support for focusing windows from within Dasher
* Bump version to 3.2.12
