[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]
Re: 2013Q2 MesaLib and pbulk
On Tue, Sep 03, 2013 at 06:06:11AM +0000, David Holland wrote:
> On Sun, Sep 01, 2013 at 12:52:29PM +0200, Manuel Bouyer wrote:
> > > Does x11-links skip it? The usual issue is that x11-links skips
> > > builtin versions that are older than the minimum accepted pkgsrc
> > > version... so when that version is changed for a revbump the native X
> > > version gratuitously stops working.
> > But then the a depend should be added to the pkgsrc version, isn't it ?
> In theory; in practice this doesn't always work, or works only for
> packages that have been explicitly hacked to support it, or something.
> > Where is defined the minimum accepted pkgsrc version ?
> > MesaLib just includes dri2proto/buildlink3.mk, and dri2proto/buildlink3.mk
> > has:
> > BUILDLINK_API_DEPENDS.dri2proto+= dri2proto>=2.0
> > the base system has 2.1
> Then it should be in x11-links; look in
> If it's not there, and other parts of dri2proto aren't there either,
> then it must be getting skipped for some other reason. If it's not
> there but other parts of dri2proto are there, then probably it isn't
> part of the file list in x11-links. If it's there but it isn't getting
> buildlinked, that's a whole different set of problems...
indeed it's not there:
# ls /usr/pkg/share/x11-links/lib/pkgconfig/
bigreqsproto.pc renderproto.pc xevie.pc xprintapputil.pc
compositeproto.pc resourceproto.pc xext.pc xprintutil.pc
damageproto.pc scrnsaverproto.pc xextproto.pc xproto.pc
evieproto.pc sm.pc xf86bigfontproto.pc xproxymngproto.pc
fixesproto.pc trapproto.pc xf86miscproto.pc xrandr.pc
fontcacheproto.pc videoproto.pc xfixes.pc xrender.pc
fontenc.pc x11.pc xfontcache.pc xres.pc
fontsproto.pc xau.pc xi.pc xscrnsaver.pc
glproto.pc xaw6.pc xinerama.pc xt.pc
ice.pc xaw7.pc xineramaproto.pc xtrans.pc
inputproto.pc xbitmaps.pc xkbfile.pc xtrap.pc
kbproto.pc xcmiscproto.pc xkbui.pc xtst.pc
libfs.pc xcomposite.pc xmu.pc xv.pc
printproto.pc xcursor.pc xmuu.pc xvmc.pc
randrproto.pc xdamage.pc xp.pc xxf86misc.pc
recordproto.pc xdmcp.pc xpm.pc xxf86vm.pc
so it's a x11-links problem ? Any idea how to fix it ?
Manuel Bouyer <bouyer%antioche.eu.org@localhost>
NetBSD: 26 ans d'experience feront toujours la difference
Main Index |
Thread Index |