Hans Leidekker hans at
Fri Jun 15 13:04:01 CDT 2007

On Friday 15 June 2007 18:23:51 Brian Vincent wrote:

> While this strikes me as 100% a packaging issue, it just seems like
> something really prone to error.  When the new Foo distro comes out
> and decides to place their fonts in /opt/Foo/X they'll need to figure
> out how to make the sym links, but then maybe they won't include these
> fonts, so the package maintainer will have to make another package and
> ship it alongside Wine.  That'll work great until Wine gets ported
> some other OS that doesn't include the fonts, then that maintainer
> will have to deal with some odd scheme.

In my scenario the symlinks point to files that the Wine packager knows
where they are because he put them there.

Say we have a wine-fonts subpackage that holds the modified versions
of the liberation fonts and the install prefix is /usr/local. Then we
know that Wine's fonts will be in /usr/local/share/wine/fonts and so
wineprefixcreate would create a link like this:

  ~/.wine/drive_c/windows/fonts/arial.ttf -> /usr/local/share/wine/fonts/arial.ttf


More information about the wine-devel mailing list