head	1.2;
access;
symbols
	RELEASE_8_3_0:1.2
	RELEASE_9_0_0:1.2
	RELEASE_7_4_0:1.2
	RELEASE_8_2_0:1.2
	RELEASE_6_EOL:1.2
	RELEASE_8_1_0:1.2
	RELEASE_7_3_0:1.2
	RELEASE_8_0_0:1.1
	RELEASE_7_2_0:1.1
	RELEASE_7_1_0:1.1
	RELEASE_6_4_0:1.1
	RELEASE_5_EOL:1.1
	RELEASE_7_0_0:1.1
	RELEASE_6_3_0:1.1
	PRE_XORG_7:1.1
	RELEASE_4_EOL:1.1
	RELEASE_6_2_0:1.1
	RELEASE_6_1_0:1.1
	RELEASE_5_5_0:1.1
	RELEASE_6_0_0:1.1
	RELEASE_5_4_0:1.1
	RELEASE_4_11_0:1.1;
locks; strict;
comment	@# @;


1.2
date	2009.12.21.02.15.39;	author dougb;	state Exp;
branches;
next	1.1;

1.1
date	2004.12.31.14.33.16;	author lioux;	state Exp;
branches;
next	;


desc
@@


1.2
log
@For ports maintained by ports@@FreeBSD.org, remove names and/or
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.
@
text
@[ excerpt from developer's web site ]

JZlib is a re-implementation of zlib in pure Java. The first and
final aim for hacking this stuff is to add the packet compression
support to pure Java SSH systems.

- Why JZlib?

Java Platform API provides packages 'java.util.zip.*' for accessing
to zlib, but that support is very limited if you need to use the
essence of zlib. For example, we needed to full access to zlib to
add the packet compression support to pure Java SSH system, but
they are useless for our requirements. The Internet draft SSH
Transport Layer Protocol says in the section '4.2 Compression' as
follows,

WWW: http://www.jcraft.com/jzlib/
@


1.1
log
@New port jzlib version 1.0.5: A re-implementation of zlib in pure Java
@
text
@a17 2

-- lioux@@FreeBSD.org
@

