Overview of changes from 1.0.0 to 1.0.1
==
* Fixes
o Minor
- uim-xim
- Workaround fix for preventing SEGV if compiled with g++-4.x.
Overview of changes from 1.0.0-beta to 1.0.0-final
==
* Fixes
o Minor
- uim.el
- Sync with uim-el 0.0.6-beta4
- gtk+ immodule
- fix SEGV with gvim when the caret state indicator is enabled
with a timeout value (Etsushi)
- workaround fix for preedit handling on gvim when use-with-vi?
is enabled with anthy and mana (Masanari, YamaKen, Etsushi)
- SKK
- improve completion behavior (Masanari, Etsushi)
Overview of changes from 1.0.0-alpha to 1.0.0-beta
==
* New features
o IM related
- SKK
- enable word completion with UNIX look command (Etsushi)
* Fixes
o Critical
- uim-pref-qt
- fix behavior of custom widget with integer number when the
value in the stored file is greater than 99 (Etsushi)
o Minor
- update configure script (Etsushi)
- don't require XML::Parser
- more strict check for canna
- Qt immodule
- fix to respond to uim-pref-gtk's custom messages on the fly in
addition to uim-pref-qt's (Etsushi)
- uim-pref-qt
- code cleanup (Kazuki)
- Canna
- fix behavior of backspace key in conversion state (Etsushi)
o Others
- Update translations
Overview of changes from 0.4.9.1 to 1.0.0-alpha
==
* New features
o Main features
- uim.el (bridge for Emacs) (Konosuke)
- byeoru Hangul input suite (Jae-hyeon)
- mana Japanese input (Masanari)
o IM related
- toggle-im facility (Etsushi, YamaKen)
- Anthy
- vi-cooperative mode (Masanari)
- Canna
- vi-cooperative mode (Masanari)
- SKK (Etsushi)
- dynamic completion
- ddskk compatible behavior with mistypes while starting
kanji-mode, e.g. "kAnnji" for "Kannji"
- improved numeric conversion
- support commit with opposite case in latin-conversion
- support completion with conversion and/or commit at once
* Fixes
o Critical
- fix segmentation fault if uim is compiled with '--enabled-debug'
(Etsushi, dai <d+r AT vdr.jp>)
- fix IPC (connection to PRIME) in some rare cases (Masanari)
- fix possible GC crash with anti-stack smashing compilers such as
GCC4 (Jun, YamaKen)
o Minor
- preedit reset with IM switch (Masanari)
- some build fixes (Masanari)
- gtk+ immodule
- disable warnings (Etsushi)
- uim-xim
- support changes in X modifier keys on-the-fly (Etsushi)
- Anthy
- improve kana-input mode (Masanari)
- SKK
- improve completion behavior (Etsushi)
- improve skkserv connection (Masahito, Etsushi)
- PRIME
- proper custom setting (YamaKen)
- uim-im-switcher-qt
- show list of IM properly (Etsushi)
- uim-pref-qt
- compatible behavior with uim-pref-gtk (Etsushi)
* Others
o obsolete table API
o translations
- add ko (Jae-hyeon)
- update ja (Daichi Kawahata, YamaKen)
ChangeLog (extracted manually, probably incomplete):
0.4.9.1:
Security fix:
If you are using setuid/setgid application which is linked to libuim,
you have to upgrade uim.
0.4.9:
Memory leak and bug fixes.
0.4.8:
Bug fixes and updates for uim-anthy, uim-prime, uim-skk, and uim-romaja.
0.4.7:
Many bug fixes.
1) Simplify the way how an emacs version is picked when no emacs
is installed, but a user try to install an Emacs Lisp package.
Just pick up the version set as EMACS_TYPE than searching for
versions already installed etc. If the EMACS_TYPE version is
not supported by the Emacs Lisp Package, just fail. EMACS_TYPE
be default to GNU Emacs 21.
(In other words, users should set EMACS_TYPE as they want.
Otherwise GNU Emacs 21 is used.)
2) All Emacs Lisp Packages *must* prepend EMACS_PKGNAME_PREFIX to
a) the PKGNAME itself, and b) PKGNAME in its dependency lines.
EMACS_PKGNAME_PREFIX is expanded to "xemacs-" when XEmacs is
used. This keeps dependency graph of Emacs-Lisp-packages-
installed-for-XEmacs consistent.
3) Document EMACS_* variables as much as possible.
4) Provide more cookies for PLIST. Maybe utilized later.
Note that the 2) change doesn't affect the default, GNU Emacs 21
behaviour. So no version / revision bumps in this commit.
backslashes anymore. A single backslash is enough. Changed the
definition in all affected packages. For those that are not caught, an
additional check is placed into bsd.pkginstall.mk.
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.
And always is defined as share/examples/rc.d
which was the default before.
This rc.d scripts are not automatically added to PLISTs now also.
So add to each corresponding PLIST as required.
This was discussed on tech-pkg in late January and late April.
Todo: remove the RCD_SCRIPTS_EXAMPLEDIR uses in MESSAGES and elsewhere
and remove the RCD_SCRIPTS_EXAMPLEDIR itself.
Yamashiro.
Changes in 0.4.6:
A GUI preference tool was introduced, both for Gtk and Qt. uim-kdehelper and
UimQt were merged. A plugin system was introduced.
Package changes:
conversion engine anthy or canna can select by setting the
PKG_OPTIONS.uim variable.
buildlink3.mk added.
ChangeLog:
* cannadic/ update to cannadic-0.95c
* src/splitter/commit.c fix mis-computation of segment length which
can cause out of array bound access
* use Hidden Markov Model to find segment boundary.
I added a message recommending the installation of inputmethod/anthy
if one is interested in Japanese input.
Uim is a lightweight and full featured multilingual input method library
and is simple, secure and flexible.
under share/examples/rc.d. The variable name already was named
RCD_SCRIPTS_EXAMPLEDIR.
This is from ideas from Greg Woods and others.
Also bumped PKGREVISION for all packages using RCD_SCRIPTS mechanism
(as requested by wiz).
under ${PREFIX} instead of being an absolute path.
So fix the references using RCD_SCRIPTS_EXAMPLEDIR to be
${PREFIX}/${RCD_SCRIPTS_EXAMPLEDIR}.
This should have no changes to use before.
Please note that the MESSAGE files in most cases are wrong in the
first place. We have automated mechanisms and could have an automated
message for explaining rc.d script usage. (This is something to do!)
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:
- Provide a configuration window.
- Better support Java applications.
- Increase the number of entries to 9 in the Hanja/symbol input list.
- Print warning for non-supported locales.
- Support Korean input with en_US.UTF-8.
which installs to ${RCD_SCRIPTS_EXAMPLEDIR}. But the MESSAGE
referred to wrong hard-coded location if the RCD_SCRIPTS_EXAMPLEDIR
was not the default. So use RCD_SCRIPTS_EXAMPLEDIR instead.
PKGREVISION not bumped because if someone had changed
RCD_SCRIPTS_EXAMPLEDIR before recent change of autoregistration
of rc.d script in PLIST, then it could not have been packaged
in first place.
Note that this commit does not imply that the MESSAGE is correct.
In some cases, the MESSAGE is clearly wrong such as suggesting
running the rc.d script from the example directory (which will work
although).
the RCD_SCRIPTS rc.d script(s) to the PLIST.
This GENERATE_PLIST idea is part of Greg A. Woods'
PR #22954.
This helps when the RC_SCRIPTS are installed to
a different ${RCD_SCRIPTS_EXAMPLEDIR}. (Later,
the default RCD_SCRIPTS_EXAMPLEDIR will be changed
to be more clear that they are the examples.)
These patches also remove the etc/rc.d/ scripts from PLISTs
(of packages that use RCD_SCRIPTS). (This also removes
now unused references from openssh* makefiles. Note that
qmail package has not been changed yet.)
I have been doing automatic PLIST registration for RC_SCRIPTS
for over a year. Not all of these packages have been tested,
but many have been tested and used.
Somethings maybe to do:
- a few packages still manually install the rc.d scripts to
hard-coded etc/rc.d. These need to be fixed.
- maybe remove from mk/${OPSYS}.pkg.dist mtree specifications too.
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.
