summaryrefslogtreecommitdiff
path: root/devel/spiff
AgeCommit message (Collapse)AuthorFilesLines
2008-07-09Fix a segfault on NetBSD/amd64 (at least):bjs6-38/+130
- Include standard headers (stdlib.h, string.h, stdio.h) in misc.h to avoid conflicts with built-in declarations of functions. - Change CFLAGS= in Makefile to CFLAGS+= to use pkgsrc-provided CFLAGS. - Include termcap.buildlink3.mk to handle termcap properly. - Add DESTDIR support, use AUTO_MKDIRS. - Bump PKGREVISION. Now I can actually use it! ;)
2007-10-05Made the package work on Solaris, which didn't like redeclarations ofrillig3-6/+38
standard functions: "misc.h", line 42: identifier redeclared: sprintf
2006-06-08Make this package build with gcc-4.minskim3-1/+31
2006-03-04Point MAINTAINER to pkgsrc-users@NetBSD.org in the case where nojlam1-2/+2
developer is officially maintaining the package. The rationale for changing this from "tech-pkg" to "pkgsrc-users" is that it implies that any user can try to maintain the package (by submitting patches to the mailing list). Since the folks most likely to care about the package are the folks that want to use it or are already using it, this would leverage the energy of users who aren't developers.
2005-02-23Add RMD160 digests.agc1-1/+2
2004-12-03Rename ALL_TARGET to BUILD_TARGET for consistency with other *_TARGETs.wiz1-2/+2
Suggested by Roland Illig, ok'd by various.
2004-07-04Apply patch by Roland Illig posted to tech-pkg to make this compilejschauma2-4/+4
on Linux.
2003-07-17s/netbsd.org/NetBSD.org/grant1-2/+2
2003-06-02Use tech-pkg@ in favor of packages@ as MAINTAINER for orphaned packages.jschauma1-2/+2
Should anybody feel like they could be the maintainer for any of thewe packages, please adjust.
2001-11-01Move pkg/ files into package's toplevel directoryzuntum3-3/+3
2001-10-15Initial import of spiff-1.0 into the Packages Collection.agc7-0/+139
Spiff compares the contents of file1 and file2 and prints a description of the important differences between the files. White space is ignored except to separate other objects. Spiff maintains tolerances below which differences between two floating point numbers are ignored. Differences in floating point notation (such as 3.4 3.40 and 3.4e01) are treated as unimportant. User specified delimited strings (i.e. comments) can also be ignored. Inside other user specified delimited strings (i.e. quoted strings) whitespace can be significant. Taken from a hint by Alan Barrett.