Searches without login should now work. You must get asked to click a button.
Port details
naimConsole ncurses-based AIM, ICQ, IRC, and Lily client
0.11.8.3.2net-imΣ=2 0.11.8.3.2Version of this port present on the latest quarterly branch.
BROKEN: Unfetchable (google code has gone away) DEPRECATED: Unfetchable for more than six months (google code has gone away) This port expired on: 2017-04-30 IGNORE: is marked as broken: Unfetchable (google code has gone away)
There is no maintainer for this port.
Any concerns regarding this port should be directed to the FreeBSD Ports mailing list via ports@FreeBSD.org
naim is a console client for AOL Instant Messenger (AIM), AOL I Seek You
(ICQ), Internet Relay Chat (IRC), and The lily CMC.
It includes unique features like zero-configuration peer to peer encryption,
automatic message queueing, and incoming message modification (to correct
common spelling mistakes and expand common abbreviations; see /help filter).
It also includes powerful dynamic module support, allowing developers to
modify all major aspects of naim's behavior.
When combined with GNU Screen, naim is great to use as a chat client as
well as an answering machine. Individual users can detach, log out, pack
up and go home, then log back in from anywhere on the Internet to resume
their naim session.
WWW: http://naim.n.ml.org/
===> The following configuration options are available for naim-0.11.8.3.2:
DETACH=off: Enable 'detach' feature (requires misc/screen)
DOCS=on: Build and/or install documentation
===> Use 'make config' to modify these settings
2017-04-30 devel/stormlib-ghost++: Unfetchable for more than six months (google
code has gone away)
2017-04-30 devel/py-coil: Unfetchable for more than six months (google code has
gone away)
2017-04-30 devel/py-cmdln: Unfetchable for more than six months (google code has
gone away)
2017-04-30 devel/privman: Unfetchable for more than six months (google code has
gone away)
2017-04-30 devel/c-unit: Unfetchable for more than six months (google code has
gone away)
2017-04-30 devel/py-px: Unfetchable for more than six months (google code has
gone away)
2017-04-30 devel/nglogc: Unfetchable for more than six months (google code has
gone away)
2017-04-30 devel/bncsutil-ghost++: Unfetchable for more than six months (google
code has gone away)
2017-04-30 devel/liblouisxml: Unfetchable for more than six months (google code
has gone away)
2017-04-30 devel/nxt-python: Unfetchable for more than six months (google code
has gone away)
2017-04-30 devel/spdict: Unfetchable for more than six months (google code has
gone away)
2017-04-30 devel/guiloader-c++: Unfetchable for more than six months (google
code has gone away)
2017-04-30 devel/streamhtmlparser: Unfetchable for more than six months (google
code has gone away)
2017-04-30 devel/winpdb: Unfetchable for more than six months (google code has
gone away)
2017-04-30 net/opendpi: Unfetchable for more than six months (google code has
gone away)
(Only the first 15 lines of the commit message are shown above )
Mark the remaining ports depending on Google Code as DEPRECATED, with an
EXPIRATION_DATE at the end of April 2017.
In the past six months, about a third of the ports marked BROKEN because
they were hosted on Google Code have been fixed. The remaining must not
be of use to anyone.
With hat: portmgr
Sponsored by: Absolight
GOOGLE_CODE has gone away.
- If a port has another upstream, remove GOOGLE_CODE
- If a port only has GOOGLE_CODE mark it BROKEN
Some ports have a local mirror configured but for security reasons, it
is not considered upstream.
Sponsored by: Absolight
- Fix targets' dependencies in an attempt to fix parallel (-jX) builds
- While here: contract MASTER_SITES, restore original DETACH_DESC (pre-
r324947; timeout from jgh@ since May 24), add DOCS to OPTIONS_DEFINE,
define LICENSE (GPLv2)
- In pkg-descr: kill EOL spaces and terminate URL with a slash as told
by PH, section 3.2.1)
Reported by: marino
Approved by: miwi, bapt (portmgr, implicit)
Update CONFIGURE_ARGS for how we pass CONFIGURE_TARGET to configure script.
Specifically, newer autoconf (> 2.13) has different semantic of the
configure target. In short, one should use --build=CONFIGURE_TARGET
instead of CONFIGURE_TARGET directly. Otherwise, you will get a warning
and the old semantic may be removed in later autoconf releases.
To workaround this issue, many ports hack the CONFIGURE_TARGET variable
so that it contains the ``--build='' prefix.
To solve this issue, under the fact that some ports still have
configure script generated by the old autoconf, we use runtime detection
in the do-configure target so that the proper argument can be used.
Changes to Mk/*:
- Add runtime detection magic in bsd.port.mk
(Only the first 15 lines of the commit message are shown above )
- Set --mandir and --infodir in CONFIGURE_ARGS if the configure script
supports them. This is determined by running ``configure --help'' in
do-configure target and set the shell variable _LATE_CONFIGURE_ARGS
which is then passed to CONFIGURE_ARGS.
- Remove --mandir and --infodir in ports' Makefile where applicable
Few ports use REINPLACE_CMD to achieve the same effect, remove them too.
- Correct some manual pages location from PREFIX/man to MANPREFIX/man
- Define INFO_PATH where necessary
- Document that .info files are installed in a subdirectory relative to
PREFIX/INFO_PATH and slightly change add-plist-info to use INFO_PATH and
subdirectory detection.
PR: ports/111470
Approved by: portmgr
Discussed with: stas (Mk/*), gerald (info related stuffs)
Tested by: pointyhat exp run
