[Foresight-devel] Re: kdelibs

[António Meireles]

Hi,
i had a similar issue on 2-devel. It seemed a very subtle conary bug. 
Basically we had several aditional troves providing libGL (besides Mesa) 
and somehow kdelibs tended to pick (and prefer) nvidia's one.
(had to do with searchPaths)
This vanished in late conary-2.0 releases.

Re: on your context - replace

*resolveTroves Mesa:devel=foresight.rpath.org at fl:1-devel['!ati,!nvidia']*
*resolveTroves Mesa:devellib=foresight.rpath.org at fl:1-devel['!ati,!nvidia']*


by just  *resolveTroves 
Mesa=foresight.rpath.org at fl:1-devel['!ati,!nvidia'] *

or (more correct) by

*resolveTroves group-dist=foresight.rpath.org at fl:1-devel**['!ati,!nvidia'] 
*


way saner, not sure if will have any impact on this.


Will look both at this once i'm online on IRC, either later today or 
tomorrow.


have a great weekend,

António



Thilo Pfennig wrote:
> Hi António,
>
> Ken said I should contact you as I had committed kdelibs=@fl:1-devel
> with nvidia:devellibs, because that was the only way to get Mesa libs.
> there was no other way because Mesa:devel did nothing.
>
> my current context looks like this:
>
> [fl:1-devel]
> buildLabel                foresight.rpath.org at fl:1-devel
> installLabelPath          foresight.rpath.org at fl:1-devel
> foresight.rpath.org at fl:1-contrib conary.rpath.com at rpl:1 co
> ntrib.rpath.org at rpl:1 orleans.rpath.org at rpl:devel 
> resolveTroves Mesa:devel=foresight.rpath.org at fl:1-devel['!ati,!nvidia']
> resolveTroves
> Mesa:devellib=foresight.rpath.org at fl:1-devel['!ati,!nvidia']
> resolveTroves conary=conary.rpath.com at rpl:1-devel 
> resolveTroves conary-build=conary.rpath.com at rpl:1-devel 
> resolveTroves group-dist=foresight.rpath.org at fl:1-devel
>
> autoResolve True
>