Changes since last packaged version (1.10):
* errors in tags error files are reported more correctly and make
the program exit
* more tag options added
* "linenum" tag for specifying the style of line numbers
Package changes:
* set USE_LANGUAGES
* fix HTML installation directory in manpage
which was the BUILDLINK_RECOMMENDED.xmlcatmgr. (Okay'ed by jmmv.)
I had noticed that old xmlcatmgr on my system (using IGNORE_RECOMMENDED)
was not good enough
The xmlcatmgr changes for 2.0alpha2 said that command line usage changed
in some scenarios.
Also remove BUILDLINK_RECOMMENDED.xmlcatmgr because now it was the
same (and is redundant for now).
I am not bumping in PKGREVISIONs because of this. This happened
last January and is too late now and maybe I am the only person to
notice.
in the process. (More information on tech-pkg.)
Bump PKGREVISION and BUILDLINK_DEPENDS of all packages using libtool and
installing .la files.
Bump PKGREVISION (only) of all packages depending directly on the above
via a buildlink3 include.
we were running intltoolize before the configure stage, which replaced all
intltool-*.in files with symlinks to the ones installed by this package.
However, the new version of intltool, 0.31.3, has added new substitution
patterns to the scripts, which must be replaced by configure scripts at
configuration time. The problem is that old configure scripts (pre-0.31.3)
do not know about these patterns, which results in them not being substituted,
thus causing build failures.
So, to fix this issue, replace all intltool-* files _after_ the configure
stage, just like we do with libtool. Additional patters might be added
through the INTLTOOL_OVERRIDE variable, but I doubt this will be needed).
While here, update the dependency to 0.31.3 (has no other effect, as this
package is only used at build time by other packages).
when needed) is correct but... no answers in tech-pkg@ for several days.
* Use absolute paths and allow env var overrides for gettext scripts
-- bug #152020 (Rodney Dawes)
* Allow shell-backticks (and other shell features) in variable names
-- bug #152448 (Danilo Segan)
* Fix typographical error in intltool.m4
-- bug #153630 (Rodney Dawes)
Pod::Simple is a Perl library for parsing text in the Pod ("plain
old documentation") markup language that is typically used for
writing documentation for Perl and for Perl modules.
Pod formatters can use Pod::Simple to parse Pod documents into
produce renderings of them in plain ASCII, in HTML, or in any number
of other formats.
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".
and getprogname.
We're using libnbcompat, so we know they exist. (If we were to check again,
then we'd mess up definitions set in the nbcompat headers.)
jlam's last change, since we use libnbcompat. (If we left these checks in,
configure would test for them, find them and set HAVE_GETPROGNAME, subsequently
breaking 'getprogname', as nbcompat.h wouldn't work since HAVE_GETPROGNAME
is then defined.)
- build fix: NUL in c file blocking compilation on Solaris, Windows build
(Igor Zlatkovic)
- fix: key initialization problem (William Brack)
- documentation: fixed missing man page description for --path
Version 0.31.2
* Handle package name extraction better
-- bug #144725 (Daniel Elstner)
* Support for comments before translatable attributes in XML files,
support for translating both tag content and attributes
-- bug #143581. (Danilo Segan)
Version 0.31.1
* Switch to gnome-common for autogen.sh so we can detect automake
versions better -- bug #145027 (Jordi Mallach)
Third stable version of the 2.x branch, released on 2004/09/01.
* Converted to use the GNU Build System (GNU Automake and GNU Autoconf).
* Because of the previous change, the build has been hopefully fixed in
several platforms, specially under Irix 6.5 using the MIPSpro C compiler.
intended transformation: use "rm" to remove an option, "rmdir" to remove
all options containing a path starting with a given directory name, and
"rename" to rename options to something else.
which are the full option names used to set rpath directives for the
linker and the compiler, respectively. In places were we are invoking
the linker, use "${LINKER_RPATH_FLAG} <path>", where the space is
inserted in case the flag is a word, e.g. -rpath. The default values
of *_RPATH_FLAG are set by the compiler/*.mk files, depending on the
compiler that you use. They may be overridden on a ${OPSYS}-specific
basis by setting _OPSYS_LINKER_RPATH_FLAG and _OPSYS_COMPILER_RPATH_FLAG,
respectively. Garbage-collect _OPSYS_RPATH_NAME and _COMPILER_LD_FLAG.