From owner-freebsd-ports Sun Feb 13 22:12:10 2000 Delivered-To: freebsd-ports@freebsd.org Received: from m3.cs.berkeley.edu (m3.CS.Berkeley.EDU [128.32.45.179]) by builder.freebsd.org (Postfix) with ESMTP id 3EED448F3 for ; Sun, 13 Feb 2000 22:12:09 -0800 (PST) Received: from silvia.hip.berkeley.edu (sji-ca6-93.ix.netcom.com [205.186.213.93]) by m3.cs.berkeley.edu (8.9.3/8.9.3) with ESMTP id WAA72022 for ; Sun, 13 Feb 2000 22:12:21 -0800 (PST) (envelope-from asami@cs.berkeley.edu) Received: (from asami@localhost) by silvia.hip.berkeley.edu (8.9.3/8.6.9) id WAA14541; Sun, 13 Feb 2000 22:12:11 -0800 (PST) Date: Sun, 13 Feb 2000 22:12:11 -0800 (PST) Message-Id: <200002140612.WAA14541@silvia.hip.berkeley.edu> X-Authentication-Warning: silvia.hip.berkeley.edu: asami set sender to asami@cs.berkeley.edu using -f To: ports@freebsd.org Subject: PR ports/16672 From: asami@cs.berkeley.edu (Satoshi Asami) Sender: owner-freebsd-ports@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hi, Authors of giflib are recommending switching over to libungif, which only creates uncompressed (i.e., not using LZW compression) GIFs to avoid infringing on Unisys's patent claims. Here are some related URLs: http://prtr-13.ucsc.edu/~badger/software/libungif/ http://prtr-13.ucsc.edu/~badger/software/libungif/giflib.shtml http://www.cloanto.com/users/mcb/19950127giflzw.html I think we should remove the giflib port and change the giflib-requiring ports to depend on libungif. The current version of libungif is supposed to be API-compatible with the last giflib, so programs that use giflib should work (theoretically) by just recompiling. What do you guys think? If this is ok I'll go change all the LIB_DEPENDS lines to point to libungif so we can fix things that break before the freeze. Satoshi To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-ports" in the body of the message