Age | Commit message (Collapse) | Author | Files | Lines |
|
fix pkg/30448
|
|
|
|
|
|
Pointed out by Dieter Baron.
|
|
|
|
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.
|
|
with PKG_SUGGESTED_OPTIONS.
|
|
|
|
set PKG_SUGGESTED_OPTIONS instead of PKG_DEFAULT_OPTIONS (which
should be set by the user only)
|
|
|
|
USE_GNU_TOOLS -> USE_TOOLS
awk -> gawk
m4 -> gm4
make -> gmake
sed -> gsed
yacc -> bison
|
|
variable definitions that apply when USE_IMAKE is defined.
|
|
Add it explicitly here until pkgsrc/mk/* can be modified to infer this
by itself.
|
|
|
|
also updated PKGREVISION of each package. works fine for me. Thank you!
|
|
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.
|
|
|
|
patch supplied from Yamashiro Jun.
fix PR pkg/29930
|
|
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.
|
|
useful.
|
|
NetBSD-1.6.2. Approved by wiz.
|
|
|
|
Bump revision.
|
|
|
|
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.
|
|
|
|
Bump PKGREVISION.
|
|
|
|
|
|
GTK2 input modules. Bump PKGREVISION.
Thanks to jmmv for the hint on how to do this (see x11/gtk2/modules.mk).
|
|
|
|
Some BUILDLINK_RECOMMENDED bumps done also.
(If I missed any, please let me know -- and let me know a good
way to automate this.)
|
|
|
|
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.
|
|
sorry.
|
|
This is a elisp frontend of inputmethod/anthy.
|
|
- add okinawa dict
patch from Jun Yamashiro <yamajun AT ofug DOT net>
|
|
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).
|
|
from Noritoshi Demizu in PR pkg/28618.
|
|
Changes:
- Support more keyboard layout.
- Update icons.
- Add Tux theme.
- Enable setting Korean/English, Hangul/Hanja switch keys.
|
|
|
|
Anthy is a free and secure Japanesse inputmethod.
|
|
Suggested by Roland Illig, ok'd by various.
|
|
because sj3-lib requires nbitools at build time only. Noted by
oshimaya at sc.starcat.ne.jp in PR pkg/25778.
|
|
|
|
Changes:
* lisp/tc-mazegaki.el: C-g can interrupt kana-kanji conversion.
* lisp/tc-is18.el:
* lisp/tc-is19.el:
* lisp/tc-is20.el: fix infinite loop bug.
* lisp/tutc-tbl.el: fix translation table.
* lisp/eelll.el: use colored background in bitmap display mode.
* skkinput3/Makefile.am: merged patches/patch-ab
|
|
|
|
|
|
|
|
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!)
|