- Changed distname.
- Removed patch for include/ircsprintf.h. It seems not needed today.
- Added patch for src/s_serv.c (it needed for custom compilation with syslog disabled)
- Removed several includes utmp.h. They are not used.
PR: ports/143008
Submitted by: "Andrey V. Elsukov" <bu7cher@yandex.ru> (maintainer)
e-mail addresses from the pkg-descr file that could reasonably
be mistaken for maintainer contact information in order to avoid
confusion on the part of users looking for support. As a pleasant
side effect this also avoids confusion and/or frustration for people
who are no longer maintaining those ports.
PR/137956 by Ashish SHUKLA (thanks!). [1]
Those ports which define EMACS_PORT_NAME to be "emacs21" were
not touched (this time). They may be converted to the new
world order by removing the above mentioned assignment.
Four ports were marked as BROKEN with EMACS_PORT_NAME=emacs23
(they do not compile):
. lang/bigloo;
. mail/wanderlust;
. mail/wanderlust-devel;
. www/emacs-w3m.
Three ports were marked as IGNORE with EMACS_PORT_NAME=emacs23:
. japanese/egg-canna (the port version is dated as of 2001,
does not compile with Emacs 23 and seems it cannot be fixed);
. deskutils/remember.el (was incorporated into Emacs 23);
. editors/nxml (was incorporated into Emacs 23).
Changes that were made after (and as a result of) exp run. For
those ports:
. japanese/migemo-emacs21;
. japanese/migemo-emacs22
EMACS_PORT_NAME?= was changed to EMACS_PORT_NAME= to the apropriate
emacs port name.
PR: ports/137956 [1], ports/141369 [2]
Submitted by: Ashish SHUKLA <wahjava at gmail.com> [1],
bsam (me) [2]
Exp-run by: miwi
See http://quassel-irc.org/pub/ChangeLog for details.
Please note, new Quassel Core will not work with old client and
vice versa. You will have to update both components. First time you
run a 0.5 core or client, the config files and database will
automatically be updated to the new format. Downgrades are not
supported, so do make a backup if you intend to go back to 0.4
afterwards!
I've add this port as a 'new' port, even though we already have
ports/irc/keitairc, keitairc 1.x. Because...
- keitairc 2.x is a _complete_ rewrite of keitairc 1.x
keitairc 1.x is just a single perl script, but keitairc 2.x
is composed of a script, Keitairc perl module, templates, etc.
Also there is no configuration file compability between 1.x and 2.x.
- keitairc 2.x port is a _complete_ rewrite of keitairc 1.x
Since the application structure is changed, I have to write
a new port for 2.x, instead of _modify_ 1.x port.
Tested by: nork
