pkgsrc - [no description]

Age	Commit message (Collapse)	Author	Files	Lines
2004-09-22	Mechanical changes to package PLISTs to make use of LIBTOOLIZE_PLIST.	jlam	1	-17/+1
	All library names listed by *.la files no longer need to be listed in the PLIST, e.g., instead of: lib/libfoo.a lib/libfoo.la lib/libfoo.so lib/libfoo.so.0 lib/libfoo.so.0.1 one simply needs: lib/libfoo.la and bsd.pkg.mk will automatically ensure that the additional library names are listed in the installed package +CONTENTS file. Also make LIBTOOLIZE_PLIST default to "yes".
2003-12-26	Update to 1.1.3:	wiz	1	-9/+10
	1.1.3: Now with shiny new Hspell support (requires hspell 0.7). Other than that, no changes have been made since the 1.1.2 release. 1.1.2: Has Jordi's Ispell bugfix in it plus the new Hspell backend. 1.1.0: New Enchant release. This fixes some ispell-compatibility mode problems (i.e. the command line program), specifically related to charsets. This also fixes some other charset issues that affected our Ispell and Myspell backends. Big thanks to Raphael Finkel and egmont@uhulinux.hu (Egmont Koblinger) Everyone is strongly encouraged to upgrade. It exports 1 more function and maintains API/ABI compability. AbiWord 2.1.0 depends on this released version or a CVS equivalent. 1.0: :)
2003-09-17	Initial import of enchant, a generic spell checking library.	wiz	1	-0/+29
	The project aims to provide an efficient extensible abstraction for dealing with different spell checking libraries. Enchant is meant to provide a generic interface into various existing spell checking libaries. These include, but are not limited to: * Aspell/Pspell * Ispell * Hspell * Uspell Enchant is also meant to be used in a cross-platform (XP) environment. Part of this means that Enchant wants to limit its number of external dependencies to 0, or as close is as humanly possible. Also, any enchant consumer (i.e. a Word Processor) should not need to know about what backend providers Enchant knows about. In fact, Enchant shouldn't even need to know this information itself. To accomplish this, all of Enchant's providers are DLLs. Enchant is also meant to be used in a multi-user environment, such as Unix. It is preferable to have both a $USER and a $GLOBAL location for both provider DLLs and for dictionaries themselves, when possible. Enchant's DLL location algorithm takes this into account, and gives preference to the $USER DLLs, when found.