caches for individuals as needed.
Remove gnome from CATEGORIES.
Redo the added font paths because ${LOCALBASE}/lib/X11/fonts is
already default as configured above, so don't need to add again.
And don't need to list sub-directories of "fonts" because fontconfig
already looks in sub-directories too. (I have been using this over
a year on various systems like this.)
Update to 2.3.2. Changes include:
* fc-cache/fc-cache.c: (scanDirs):
Fix a few minor leaks in error cases.
* fc-cache/fc-cache.c: (main):
Destroy font configuration on exit to help valgrind
* fonts.conf.in:
* src/fcfreetype.c: (FcSfntNameTranscode), (FcFreeTypeCharIndex),
(FcFreeTypeCheckGlyph):
Use own transcoding routines in preference to iconv
which appears to have leaks in some translators.
Call iconv_close after using iconv (oops).
Prefer unicode encoding of Euro char as some
fonts mis-encode Euro in other ones.
Must fetch bitmap glyphs to get width values
to check for monospace/dual-width fonts.
Complete changes at
http://www.fontconfig.org/release/ChangeLog-2.3.2
Note that manpage for fc-cache(1) is not installed yet. It is in SGML.
Also note that the new version provides same library version
libfontconfig.so.1.0.4. This was reported to developer and was an
accidently oversite. Nevertheless, it is still ABI compatible.
the X11 distribution using imake into mk/buildlink3/imake-check.mk.
imake-check.mk calls out to a helper shell script mk/buildlink3/imake-check
that generates the required Imakefiles and runs imake. Remove the
now extraneous builtin-imake.mk files as the builtin.mk files can now
contain the name of the imake symbol to check.
contain a command plus arguments. We use the standard idiom to extract
the first word of a list stored in a make variable:
VAR_CMD= ${VAR:C/^/_asdf_/1:M_asdf_*:S/^_asdf_//}
XXX This can be replaced with a more succinct use of variable modifiers
XXX when we update the bootstrap bmake to match the latest NetBSD make
XXX sources, i.e.:
XXX
XXX VAR_CMD= ${VAR:[1]}
Several changes are involved since they are all interrelated. These
changes affect about 1000 files.
The first major change is rewriting bsd.builtin.mk as well as all of
the builtin.mk files to follow the new example in bsd.builtin.mk.
The loop to include all of the builtin.mk files needed by the package
is moved from bsd.builtin.mk and into bsd.buildlink3.mk. bsd.builtin.mk
is now included by each of the individual builtin.mk files and provides
some common logic for all of the builtin.mk files. Currently, this
includes the computation for whether the native or pkgsrc version of
the package is preferred. This causes USE_BUILTIN.* to be correctly
set when one builtin.mk file includes another.
The second major change is teach the builtin.mk files to consider
files under ${LOCALBASE} to be from pkgsrc-controlled packages. Most
of the builtin.mk files test for the presence of built-in software by
checking for the existence of certain files, e.g. <pthread.h>, and we
now assume that if that file is under ${LOCALBASE}, then it must be
from pkgsrc. This modification is a nod toward LOCALBASE=/usr. The
exceptions to this new check are the X11 distribution packages, which
are handled specially as noted below.
The third major change is providing builtin.mk and version.mk files
for each of the X11 distribution packages in pkgsrc. The builtin.mk
file can detect whether the native X11 distribution is the same as
the one provided by pkgsrc, and the version.mk file computes the
version of the X11 distribution package, whether it's built-in or not.
The fourth major change is that the buildlink3.mk files for X11 packages
that install parts which are part of X11 distribution packages, e.g.
Xpm, Xcursor, etc., now use imake to query the X11 distribution for
whether the software is already provided by the X11 distribution.
This is more accurate than grepping for a symbol name in the imake
config files. Using imake required sprinkling various builtin-imake.mk
helper files into pkgsrc directories. These files are used as input
to imake since imake can't use stdin for that purpose.
The fifth major change is in how packages note that they use X11.
Instead of setting USE_X11, package Makefiles should now include
x11.buildlink3.mk instead. This causes the X11 package buildlink3
and builtin logic to be executed at the correct place for buildlink3.mk
and builtin.mk files that previously set USE_X11, and fixes packages
that relied on buildlink3.mk files to implicitly note that X11 is
needed. Package buildlink3.mk should also include x11.buildlink3.mk
when linking against the package libraries requires also linking
against the X11 libraries. Where it was obvious, redundant inclusions
of x11.buildlink3.mk have been removed.
* Fix manuals in section 3 so they get built and installed.
* Rework GSUB/GPOS script parsing to avoid crashing when presented
with broken fonts.
* Add a few more example configuration files to /etc/fonts/conf.d
from the debian packaging.
Fix memory leak of patterns rejected by configuration (#2518)
Create prototype $PREFIX/etc/fontconfig/conf.d directory and populate
it with a few sample files. These samples are unused as the file
names don't start with numbers.
Update documentation.
Fontconfig 2.2.99 contains a few minor bug fixes plus the addition of
polite type warnings for the config file. This latter change could use a
bit of exposure to existing config files to see if it whines about
legitimate configurations.
changes:
2.2.97
Fc-cache sleeps before exiting to ensure filesystem timestamps are well
ordered.
Added Punjai orthography.
The timestamp in fonts.conf is gone now. Too many problems.
The default font path includes all of the X fonts; use selectfont/rejectfont
to eliminate bitmaps, as shown in the sample local.conf file.
<include> configuration elements may now reference a directory. Files
in that directory matching [0-9]* are loaded in UTF-8 collating sequence order.
<selectfont> configuration added to control which fonts are used.
fontformat font pattern elements built from the FT_Get_X11_Font_Format
function in newer versions of FreeType.
'capability' list constructed from gsub/gpos and silf values in TrueType
files.
Multi-lingual names (style, family, fullname) extracted and stored with
parallel <foo>lang properties marking language.
2.2.98
Share object name strings (Michael Meeks)
Eliminate a couple of codepoints from Russian orthography (John Thacker)
Add synthetic emboldening configuration changes (Jakub Pavelek)
Change FcFontSetSort to ignore language after fonts with the requested
languages have been found. (Owen Taylor)
Add some RedHat font configuration changes (Owen Tayler).
Add full Unicode case folding support to case-ignoring string functions
(Keith Packard)
Remove Han characters from Korean orthography (Tor Andersson)
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.
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".
changes:
2004-06-30 Keith Packard <keithp@keithp.com>
* README:
* configure.in:
* fontconfig/fontconfig.h:
Update for 2.2.96
2004-06-30 Keith Packard <keithp@keithp.com>
Provided by: Lubos Lunak <l.lunak@suse.cz>
* src/fccfg.c: (FcConfigUptoDate):
However FcConfigUptoDate() doesn't seem to work. See the attached
patch. First there's an obvious misplaced parenthesis making it
return always false, and second, even this call fails to detect font
changes (e.g. adding a new font to
/usr/X11R6/lib/X11/fonts/truetype). The patch should fix that as
well. The problem seems to be triggered by my fonts.conf specifying
only /usr/X11R6/lib/X11/fonts , and therefore config->configDirs
doesn't include subdirs, unlike config->fontDirs.
2004-06-03 Keith Packard <keithp@keithp.com>
* fontconfig/fontconfig.h:
Remove comma at end of FcResult enum definition.
2004-05-29 Keith Packard <keithp@keithp.com>
* INSTALL:
Add steps to md5sum release
in particular this fixes a problem where no font matches can be found
by gtk2 apps. This should fix the problem where even the gtk-demo
program fails run.
by moving the inclusion of buildlink3.mk files outside of the protected
region. This bug would be seen by users that have set PREFER_PKGSRC
or PREFER_NATIVE to non-default values.
BUILDLINK_PACKAGES should be ordered so that for any package in the
list, that package doesn't depend on any packages to the left of it
in the list. This ordering property is used to check for builtin
packages in the correct order. The problem was that including a
buildlink3.mk file for <pkg> correctly ensured that <pkg> was removed
from BUILDLINK_PACKAGES and appended to the end. However, since the
inclusion of any other buildlink3.mk files within that buildlink3.mk
was in a region that was protected against multiple inclusion, those
dependencies weren't also moved to the end of BUILDLINK_PACKAGES.
built-in or not into a separate builtin.mk file. The code to deal
checking for built-in software is much simpler to deal with in pkgsrc.
The buildlink3.mk file for a package will be of the usual format
regardless of the package, which makes it simpler for packagers to
update a package.
The builtin.mk file for a package must define a single yes/no variable
USE_BUILTIN.<pkg> that is used by bsd.buildlink3.mk to decide whether
to use the built-in software or to use the pkgsrc software.
practically verbatim with the "1.0.1" release that's in XFree86 4.3.x.
There have in fact been only function additions to the fontconfig API
since 2.0, so fontconfig has never actually had a bump in the shared
library major. Therefore, allow "fontconfig>=1.0.1" as the base
requirement.
Even 2.0.9 is not good enough for newer fontconfig; for example,
gtk2 won't buildlink correctly (and will use older X version of
include/freetype2/freetype/ftbdf.h) and libfontconfig needs
FT_Get_BDF_Property which is not defined.
No PKGREVISION bump is needed, because would not even build in
first place.
the normal case when BUILDLINK_DEPENDS.<pkg> isn't specified, it receives
a value only once due to the multiple inclusion protection in the
bulldlink3.mk files. In the case where a package includes several
buildlink3.mk files that each want a slightly different version of another
dependency, having BUILDLINK_DEPENDS.<pkg> be a list allows for the
strictest <pkg> dependency to be matched.
