pkgsrc - [no description]

Age	Commit message (Collapse)	Author	Files	Lines
2002-09-13	Use ghostscript.mk.	jlam	1	-2/+2

2002-08-18	fix installation on systems where '.' is not in root's path.	dmcmahill	2	-1/+14

2002-06-17	Use REPLACE_PERL to substitute for the correct version of perl in	agc	1	-2/+3
	doc/translator.pl, which has the side effect of allowing the docygen package to be installed properly if you don't have '.' in your path. Bump PKGREVISION.
2002-03-17	Use ${PKGNAME_NOREV} in definition of ${WRKSRC}.	fredb	1	-2/+2

2002-03-13	Give all packages which depend on "png" a version bump, and update	fredb	1	-1/+2
	all dependencies on packages depending on "png" which contain shared libraries, all for the (imminent) update to the "png" package. [List courtesy of John Darrow, courtesy of "bulk-build".]
2002-01-14	Comment out some unneeded code that produced errors, in contrast to	wiz	4	-1/+37
	what the comment above it claims. Should fix bulk build failure.
2001-11-01	Move pkg/ files into package's toplevel directory	zuntum	2	-1/+1

2001-09-04	Really depend on LaTeX and Ghostscript-- it's largely useless without it	groo	4	-9/+361
	(even generating HTML). Install documentation and examples.
2001-09-04	Import doxygen-1.2.10:	groo	5	-0/+70
	Doxygen is a documentation system for C++, Java, IDL (Corba, Microsoft and KDE-DCOP flavors) and C. It can help you in three ways: 1. It can generate an on-line documentation browser (in HTML) and/or an off-line reference manual (in LaTeX) from a set of documented source files. There is also support for generating output in RTF (MS-Word), PostScript, hyperlinked PDF, compressed HTML, and Unix man pages. The documentation is extracted directly from the sources, which makes it much easier to keep the documentation consistent with the source code. 2. Doxygen can be configured to extract the code structure from undocumented source files. This can be very useful to quickly find your way in large source distributions. The relations between the various elements are be visualized by means of include dependency graphs, inheritance diagrams, and collaboration diagrams, which are all generated automatically. 3. You can even `abuse' doxygen for creating normal documentation