Esecanna pretends to be a cannaserver and listens to canna clients.
It interprets to one of the VJE 3.0/2.5 or Wnn6 servers what they say,
then passes through to them what it results.
You'll have to install one of the esecanna modules to run it.
With this, you can use VJE 3.0/2.5 or Wnn6's smart input engine
also from the console applications.
[ canna clients ] (mule, jvim, etc.)
|| /\
\/ ||
[ esecanna ] (esecannaserver + {vje30,wnn6} module)
|| /\
\/ ||
[ input engine ] (vjed or jserver)
Further information is found on the following web site:
===> The following configuration options are available for ja-esecanna-1.0.1_6:
DOCS=on: Build and/or install documentation
===> Use 'make config' to modify these settings
Quick Setup:
Take the following steps all as root.
1) Install one of the esecanna-module ports.
2) Edit `${PREFIX}/etc/esecannarc'.
3) Stop and disable cannaserver if you have it running.
4) Run `${PREFIX}/etc/rc.d/esecanna.sh start'.
5) Add `esecanna_enable=YES' to /etc/rc.conf so that
esecanna automatically starts on (every) boot.
User can copy `${PREFIX}/etc/esecannarc' to `~/.esecannarc'
and customize it to his/her needs. If esecanna does not
work as excepted, please consult the documents under
${PREFIX}/share/doc/esecanna/ and log output kept in
`/var/log/esecanna.log'.
Note:
Using VJE-Delta 3.0 trial, esecannaserver will fail to
connect to vjed until after once you run vje.
japanese/esecanna{,-module{-vje25,-vje30,-wnn6}}: Deprecate and set expiration
date to 2025-0-31
- Dist files are no longer available as host is no longer resolvable
using multiple different resolver.
- Last update from 2000
Approved by: portmgr (blanket)
Remove WWW entries moved into port Makefiles
Commit b7f05445c00f has added WWW entries to port Makefiles based on
WWW: lines in pkg-descr files.
This commit removes the WWW: lines of moved-over URLs from these
pkg-descr files.
Approved by: portmgr (tcberner)
Add WWW entries to port Makefiles
It has been common practice to have one or more URLs at the end of the
ports' pkg-descr files, one per line and prefixed with "WWW:". These
URLs should point at a project website or other relevant resources.
Access to these URLs required processing of the pkg-descr files, and
they have often become stale over time. If more than one such URL was
present in a pkg-descr file, only the first one was tarnsfered into
the port INDEX, but for many ports only the last line did contain the
port specific URL to further information.
There have been several proposals to make a project URL available as
a macro in the ports' Makefiles, over time.
(Only the first 15 lines of the commit message are shown above )
MASTER_SITES cleanup.
- Replace ${MASTER_SITE_FOO} with FOO.
- Merge MASTER_SITE_SUBDIR into MASTER_SITES when possible. (This means 99.9%
of the time.)
- Remove occurrences of MASTER_SITE_LOCAL when no subdirectory was present and
no hint of what it should be was present.
- Fix some logic.
- And generally, make things more simple and easy to understand.
While there, add magic values to the FESTIVAL, GENTOO, GIMP, GNUPG, QT and
SAMBA macros.
Also, replace some EXTRACT_SUFX occurences with USES=tar:*.
Checked by: make fetch-urlall-list
With hat: portmgr
Sponsored by: Absolight
In the rc.d scripts, change assignments to rcvar to use the
literal name_enable wherever possible, and ${name}_enable
when it's not, to prepare for the demise of set_rcvar().
In cases where I had to hand-edit unusual instances also
modify formatting slightly to be more uniform (and in
some cases, correct). This includes adding some $FreeBSD$
tags, and most importantly moving rcvar= to right after
name= so it's clear that one is derived from the other.
Remove the FreeBSD KEYWORD from all rc.d scripts where it appears.
We have not checked for this KEYWORD for a long time now, so this
is a complete noop, and thus no PORTREVISION bump. Removing it at
this point is mostly for pedantic reasons, and partly to avoid
perpetuating this anachronism by copy and paste to future scripts.
Mass-conversion to the USE_AUTOTOOLS New World Order. The code present
in bsd.autotools.mk essentially makes this a no-op given that all the
old variables set a USE_AUTOTOOLS_COMPAT variable, which is parsed in
exactly the same way as USE_AUTOTOOLS itself.
Moreover, USE_AUTOTOOLS has already been extensively tested by the GNOME
team -- all GNOME 2.12.x ports use it.
Preliminary documentation can be found at:
http://people.FreeBSD.org/~ade/autotools.txt
which is in the process of being SGMLized before introduction into the
Porters Handbook.
Light blue touch-paper. Run.
Whoa there, boy, that's a mighty big commit y'all have there...
Begin autotools sanitization sequence by requiring ports to explicitly
specify which version of {libtool,autoconf,automake} they need, erasing
the concept of a "system default".
For ports-in-waiting:
USE_LIBTOOL=YES -> USE_LIBTOOL_VER=13
USE_AUTOCONF=YES -> USE_AUTOCONF_VER=213
USE_AUTOMAKE=YES -> USE_AUTOMAKE_VER=14
Ports attempting to use the old style system after June 1st 2004 will be
sorely disappointed.
Run esecannaserver via nohup(1) to prevent it from dying when it gets
a SIGHUP, like when the rc script is invoked from within script(1),
e.g. in portupgrade(1)'s AFTERINSTALL hook. This is just a workaround
and I'm investigating how esecannaserver fails to ignore a SIGHUP.
Approved by: portmgr (will, kris and self)
As threatened on freebsd-ports: all startup scripts know about the two options
`start' and `stop' now (unless I have forgotten any). This allows us to call
the scripts from /etc/rc.shutdown with the correct option.
