Re: native xsrc fontconfig

[maya%netbsd.org@localhost]

On Mon, May 28, 2018 at 12:50:42PM +0200, Thomas Klausner wrote:
> On Mon, May 28, 2018 at 11:30:38AM +0100, Patrick Welche wrote:
> > On Mon, May 28, 2018 at 11:12:48AM +0100, Patrick Welche wrote:
> > > [ start with "pkg_delete -r freetype2 fontconfig" on a xsrc/native box ]
> > > 
> > > xsrc provides (according to /usr/X11R7/lib/pkgconfig)
> > > 
> > > fontconfig 2.12.4
> > > freetype 18.0.13 (2.9.1 according to dist/ChangeLog)
> > 
> > To my untrained eye, it looks as though the code in
> >   /usr/pkgsrc/distfiles/freetype-2.9.1.tar.bz2
> > and xsrc/external/mit/freetype/dist are the same, yet
> > 
> > # pkg-config --modversion freetype2
> > 22.1.16                                          <- pkgsrc version
> > # pkg_delete freetype2
> > # pkg-config --modversion freetype2
> > 18.0.13                                          <- xsrc version
> > 
> > 
> > Hmm:
> > 
> > # grep version_info= /usr/xsrc/external/mit/freetype/dist/builds/unix/configure.ac
> > version_info='22:1:16'
> 
> Ok, multiple thing went wrong there.
> 
> When running 'cvs log' on doc/ChangeLog, there is a freetype-2-9-1
> tag. But when looking at doc/VERSION.DLL there is none, and
> doc/VERSIONS.TXT does not exist. So this looks like a badly merged
> import.
> 
> The other, more relevant, thing is that /usr/src/external/mit/xorg/lib/freetype/shlib_version still is:
> 
> major=18
> minor=0
> teeny=13
> 
> So hasn't been updated for quite a while.
>  Thomas

~> env PKG_CONFIG_PATH=/usr/X11R7/lib/pkgconfig/ ktruss -i pkgconf --modversion freetype2 |grep -e pc -e '\\\n'
  1522      1 pkgconf  open("/usr/X11R7/lib/pkgconfig//freetype2-uninstalled.pc", 0, 0x1b6) Err#2 ENOENT
  1522      1 pkgconf  open("/usr/X11R7/lib/pkgconfig//freetype2.pc", 0, 0x1b6) = 3
       "prefix=/usr/X11R7\nexec_prefix=${prefix}\nlibdir=${prefix}/lib\nincludedir=${prefix}/include/freetype2\n\nName: FreeType 2\nDescript"
       "22.0.16\n"

is that current?
I didn't update shlib version. base shlib version is just wrong. but there is a discussion on tech-x11 suggesting some alternate number.