void-packages/templates/intltool.tmpl
Juan RP b52d064544 Major changes to support multiple distfiles in templates.
Each template now needs to use $distfiles that accepts the full
URL to download the distfile and old $extract_sufx is now merged
on it, but this must be separated by the '@' character. Example:

distfiles="http://www.foo.org/blah-6.2@.tar.gz
http://www.foo.org/blob-1.0@.tar.bz2"

If distfiles contains multiple files defined, $wrksrc is now
mandatory.

--HG--
extra : convert_revision : 1c3fa35f148af8323ce3cbcf5732104960de6bc4
2008-10-14 07:52:29 +02:00

27 lines
1 KiB
Cheetah

# Template build file for 'intltool'.
pkgname=intltool
version=0.40.4
distfiles="
http://ftp.gnome.org/pub/GNOME/sources/intltool/0.40/$pkgname-$version@.tar.bz2"
build_style=gnu_configure
make_cmd="$XBPS_MASTERDIR/bin/gmake"
short_desc="Toolbox for internationalisation"
maintainer="Juan RP <xtraeme@gmail.com>"
checksum=2d6bf321d83a6ac6967bad8f4439af7a14d84314
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.)"