CVS log for pkgsrc/net/freenet-tools/Makefile

Up to [cvs.NetBSD.org] / pkgsrc / net / freenet-tools

Request diff between arbitrary revisions

Keyword substitution: kv
Default branch: MAIN

Comment out dead sites.

Add socket libraries and inttypes on SunOS.  Patch from Sebastian Wiedenroth.

Drop superfluous PKG_DESTDIR_SUPPORT, "user-destdir" is default these days.

DESTDIR support

give away to pkgsrc-users

Update to 0.2.25.  No offical changelog; mainly, incorporates Interix
patches originally created for pkgsrc, and adds broadcast/receive real-time
FCP commands (experimental Entropy extensions).

Add patch making all FCP protocol commands use \r\n as EOL, now required
by Freenet (\n wasn't enough).

Use "tv@NetBSD.org" as my MAINTAINER address; makes identifying me as a
PR-responsible person (such as I am ;) a little easier.

Recursive revision bump / recommended bump for gettext ABI change.

Fixed pkglint warnings. The warnings are mostly quoting issues, for
example MAKE_ENV+=FOO=${BAR} is changed to MAKE_ENV+=FOO=${BAR:Q}. Some
other changes are outlined in

    http://mail-index.netbsd.org/tech-pkg/2005/12/02/0034.html

Replaced $f with ${f} to fix a pkglint warning.

Create directories before installing files into them.

Remove USE_GNU_TOOLS and replace with the correct USE_TOOLS definitions:

	USE_GNU_TOOLS	-> USE_TOOLS
	awk		-> gawk
	m4		-> gm4
	make		-> gmake
	sed		-> gsed
	yacc		-> bison

Remove USE_BUILDLINK3 and NO_BUILDLINK; these are no longer used.

Update to 0.2.23.
(Add --ignore, --mime-none, --delete options; a couple memory alloc fixes.)

duh.org is no longer mirroring the distfile.

Freenet Tools, a set of tools usable against a Freenet or Entropy node
to insert/retrieve content by the native FCP protocol rather than the
WWW proxy.  From the DESCR:

=====

The most important tools for those who want to insert their own content as a
website into Freenet or Entropy, are the Freenet Tools (or similiar tools
from other authors :). For Freenet, there are some such programs linked from
their http://freenetproject.org) pages. Not many of them will work with
Entropy out-of-the-box, as they sometimes specialize on minor deviations in
the FCP interface. Specificially the newer tools, supporting the FEC FCP
v1.1 will fail with Entropy, as Entropy does not yet fully support the
changes to the Freenet Client Protocol. So I suggest you use ft for Entropy
for now, since I can help you there with problems or questions.

Initial revision