# Template build file for 'intltool'.
pkgname=intltool
version=0.50.2
revision=1
homepage="https://edge.launchpad.net/intltool"
distfiles="http://launchpad.net/intltool/trunk/$version/+download/$pkgname-$version.tar.gz"
build_style=gnu-configure
makedepends="perl-XML-Parser>=2.41_1 gettext"
short_desc="Toolbox for internationalisation"
maintainer="Juan RP <xtraeme@gmail.com>"
license="GPL-2"
checksum=67f25c5c6fb71d095793a7f895b245e65e829e8bde68c6c8b4c912144ff34406
long_desc="
 The intltool collection can be used to do these things:

  o Extract translatable strings from various source files (.xml.in,
    .glade, .desktop.in, .server.in, .oaf.in).

  o Collect the extracted strings together with messages from traditional
    source files (.c, .h) in po/\$(PACKAGE).pot.

  o Merge back the translations from .po files into .xml, .desktop and
    .oaf files.  This merge step will happen at build resp. installation
    time.

 The intltool package has a script, intltoolize, which copies the various
 scripts and does the other magic to your module. So users building
 from tarballs don't need intltool, only folks building from cvs.
 (This is modeled on gettextize.)"

intltool_package() {
	depends="${makedepends}"
	noarch="yes"
	pkg_install() {
		vmove usr
	}
}
