vp-build/templates/enchant/template
Juan RP dd6b45c322 Set sourcepkg to pkgname through run_template().
This removes the need for having to specify sourcepkg manually in
every package that will build subpkgs.

--HG--
extra : convert_revision : 383e4c467e84844d2f4f61ae5c5e07a5124e9cfb
2009-07-29 22:44:30 +02:00

40 lines
1.6 KiB
Plaintext

# Template file for 'enchant'
pkgname=enchant
version=1.4.2
distfiles="http://www.abisource.com/downloads/enchant/$version/enchant-$version.tar.gz"
build_style=gnu_configure
configure_args="--disable-zemberek --disable-ispell"
short_desc="Generic spell checking library"
maintainer="Juan RP <xtraeme@gmail.com>"
checksum=95c8dd998c8fb436329d204e0edde4400b889e4e26d3f8cb888c408c9a9acc6a
long_desc="
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 (intends to replace Ispell)
* Ispell (old as sin, could be interpreted as a defacto standard)
* MySpell/Hunspell (an OOo project, also used by Mozilla)
* Uspell (primarily Yiddish, Hebrew, and Eastern European
languages - hosted in AbiWord's CVS under the module \"uspell\")
* Hspell (Hebrew)
* Zemberek (Turkish)
* Voikko (Finnish)
* AppleSpell (Mac OSX)
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."
subpackages="devel"
Add_dependency build pkg-config
Add_dependency full glibc
Add_dependency full aspell
Add_dependency full hunspell
Add_dependency full glib