k on all machines.
> >
> > It looks mostly straightforward to update (new functions -> minor
> > bump),
> > but it looks like there's something odd with builds/unix/
> > freetype-config.in,
> > our file isn't the same as upstream'
chines that have been upgraded from older versions). This
> > is a
> > problem for ports which hardcode the font name like dwm and dmenu
> > as
> > there isn't any one name which will work on all machines.
> >
> > It looks mostly straightf
dcode the font name like dwm and dmenu
> as
> there isn't any one name which will work on all machines.
>
> It looks mostly straightforward to update (new functions -> minor
> bump),
> but it looks like there's something odd with builds/unix/
>
ere isn't any one name which will work on all machines.
>
> It looks mostly straightforward to update (new functions -> minor
> bump),
> but it looks like there's something odd with builds/unix/
> freetype-config.in,
> our file isn't the same as
like there's something odd with builds/unix/freetype-config.in,
our file isn't the same as upstream's last release, any suggestions on what
to do with this?
I've already posted an update to freetype-2.8, asking for a bulk build, and
Matthieu already tested it... Have you missed it for some reasons?
is is a
problem for ports which hardcode the font name like dwm and dmenu as
there isn't any one name which will work on all machines.
It looks mostly straightforward to update (new functions -> minor bump),
but it looks like there's something odd with builds/unix/freetype-config.in,
our
