On Tue, Oct 28, 2008 at 03:32:48AM +0000, David Holland wrote: > On Tue, Oct 28, 2008 at 03:01:39AM +0100, Quentin Garnier wrote: > > Thinking about it some more, I wonder why cairo would expose its > > API_DEPENDS in the bl3.mk file. It doesn't make sense to me: either > > you need a new cairo (because of ABI_DEPENDS), in which case you'll > > forcibly get the correct API_DEPENDS for cairo, or you don't, in > > which case whatever was installed along with cairo is good enough > > for it. > > Well, not quite. I think. Exposing that dependency means that > *clients* of cairo require at least pixman 0.12. If cairo re-exports > part of pixman's API, that's a perfectly reasonable statement to make. > The problem is that one picks up this piece of logic without > installing the new cairo that it applies to. But the very existence of that API/ABI cruft is to allow that. > What I don't see is why your build didn't go build a new pixman as a > result of it being out of date. Ordinarily it should have. Did you not No. gtk2 doesn't depend on pixman. gtk2 depends on cairo, and the installed package is deemed fit to build gtk2. You can't get a new pixman built directly through gtk2, it would have to go through rebuilding cairo, and that's what is not happening here. > clean or not cvs update x11/pixman? Or is the builtin logic broken? This really is a logic issue. -- Quentin Garnier - cube%cubidou.net@localhost - cube%NetBSD.org@localhost "See the look on my face from staying too long in one place [...] every time the morning breaks I know I'm closer to falling" KT Tunstall, Saving My Face, Drastic Fantastic, 2007.
Description: PGP signature