[Nix-dev] fontconfig with vim sumo

[Pjotr Prins]

When I build vim vim-7.2-huge-X11-python-tcl I get the following error
on starting gvim:

Fontconfig warning: line 26: empty font directory name ignored
No fonts found; this probably means that the fontconfig
library is not correctly configured. You may need to
edit the fonts.conf configuration file. More information
about fontconfig can be found in the fontconfig(3) manual
page and on http://fontconfig.org

when I set

  export FONTCONFIG_FILE=/etc/fonts/fonts.conf
	
it works, but obviously my Debian fonts get loaded. Using

  ls ~/.nix-profile/etc/fonts/fonts.conf

I see:

  <!-- Font directory list -->

  <dir></dir>
  <dir>/usr/X11R6/lib/X11/fonts</dir>
  <dir>~/.fonts</dir>

The first one is erroneous. But what about the second one? And how
does one use fontconfig with the Nix fonts?

Pj.


On Wed, Oct 08, 2008 at 10:09:42AM +0200, Ludovic Courtès wrote:
> Hi,
> 
> Armijn Hemel <armijn at uulug.nl> writes:
> 
> > hiya,
> >
> >> Log:
> >> Add libupnp, a UPnP implementation.
> >
> > Urgh. I suggest we add a meta.pkgCrapLevel for this one.
> >
> > Seriously, you want to replace it with pupnp (the forked and
> > *maintained* version of this library): pupnp.sourceforge.net
> 
> Can you provide a bit of explanation?  Is pupnp API-compatible?  The
> thing is software (aMule in this case) actually uses libupnp.
> 
> > UPnP security is a bit of a hobby horse for me:
> > http://www.upnp-hacks.org/
> 
> I see.  :-)
> 
> It's not clear from the front page whether the security issues you are
> concerned about stem from implementation flaws (such as buffer
> overflows, which you mention on another page) or protocol flaws (which
> you mention in the paragraph that starts with "In May 2006").  If the
> latter, it would be great to emphasize it after "very little has
> changed", IMO.
> 
> Thanks,
> Ludo'.
> 
> _______________________________________________
> nix-dev mailing list
> nix-dev at cs.uu.nl
> https://mail.cs.uu.nl/mailman/listinfo/nix-dev