23dd7d008e
- There's no need to set build_style for custom-install (default).
- gnu_{configure,makefile} renamed to gnu-{configure,makefile}.
29 lines
1.1 KiB
Text
29 lines
1.1 KiB
Text
# Template build file for 'intltool'.
|
|
pkgname=intltool
|
|
version=0.41.1
|
|
distfiles="http://launchpad.net/intltool/trunk/$version/+download/$pkgname-$version.tar.gz"
|
|
build_style=gnu-configure
|
|
short_desc="Toolbox for internationalisation"
|
|
maintainer="Juan RP <xtraeme@gmail.com>"
|
|
checksum=06d02133a85b9d6f29cd763050dc9267a6d73ef3008993f5b917cafc7ece96c0
|
|
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.)"
|
|
|
|
noarch=yes
|
|
Add_dependency full perl-XML-Parser
|
|
Add_dependency full gettext
|