summaryrefslogtreecommitdiff
path: root/devel/guile-lib
AgeCommit message (Collapse)AuthorFilesLines
2006-03-30* Honor PKGINFODIR.jlam5-24/+33
* List the info files directly in the PLIST.
2006-03-05* Teach the tools framework how to supply the pkgsrc version ofjlam1-3/+2
makeinfo if no native makeinfo executable exists. Honor TEXINFO_REQD when determining whether the native makeinfo can be used. * Remove USE_MAKEINFO and replace it with USE_TOOLS+=makeinfo. * Get rid of all the "split" argument deduction for makeinfo since the PLIST module already handles varying numbers of split info files correctly. NOTE: Platforms that have "makeinfo" in the base system should check that the makeinfo entries of pkgsrc/mk/tools.${OPSYS}.mk are correct.
2006-02-05Recursive revision bump / recommended bump for gettext ABI change.joerg1-1/+2
2005-12-06Manually override config.guess and config.sub since this packagejoerg1-1/+5
doesn't use the normal GNU configure mess.
2005-12-05Fixed pkglint warnings. The warnings are mostly quoting issues, forrillig1-3/+3
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
2005-08-10Change my email address to @NetBSD.org.gdt1-2/+2
2005-05-22Remove USE_GNU_TOOLS and replace with the correct USE_TOOLS definitions:jlam1-2/+2
USE_GNU_TOOLS -> USE_TOOLS awk -> gawk m4 -> gm4 make -> gmake sed -> gsed yacc -> bison
2005-04-11Remove USE_BUILDLINK3 and NO_BUILDLINK; these are no longer used.tv1-2/+1
2005-02-23Add RMD160 digests.agc1-1/+2
2005-01-21The makeinfo in NetBSD 1.6 is too old to build this pkg. Set TEXINFO_REQD.kristerw1-1/+2
2004-12-03Initial import of guile-lib, provided by Greg Troxel via pkgsrc-wip.wiz5-0/+142
Guile-Lib is intended as an accumulation place for pure-scheme Guile modules, allowing for people to cooperate integrating their generic Guile modules into a coherent library. Think "a down-scaled, limited-scope CPAN for Guile". Also, it can be seen as a code staging area for Guile; the Guile developers could decide to integrate some of the code into guile-core. An example for a possible candidate is SRFI-35. * SSAX, S-Exp-based XML parsing/query/conversion * HTMLPrag, a permissive ("pragmatic") HTML parser * Texinfo processing, enabling literate programming * Unit testing framework ala JUnit * Logging system * String routines (wrapping, completion, soundex algorithm) * OS process chains (think "shell pipes in scheme") * An LALR parser * ANSI escape sequence text coloring * Structured text (plain, texinfo, html) * SRFI-35 (conditions)