One more package requiring its own compiled libraries/includes on /usr. This looks more and more like a plague... People please note these things in a more careful way. This is the worst error Mandrake may carry. Right now it may be not so sensitive in a 90% Lintel environment with a very fresh distro. But a small change on processor architecture, a devel package of a previous version/build. And trouble will come. Presently I'm building packages for a PII Kalamath, for this I use a dual-Celleron machine. And I have to use a Pentium devel package to build this stuff... Now imagine a relation like: Athlon-Itanium-Pentium (yeah, it's a "stupid" relation but think about the meaning)... If we proceed this path that will break possible cross-compiling chances. More than building the package from one strike. The libraries are already there, right? On that same package that you are building right now. So why they should be "previously" located on /usr/lib???. And what if I use an old package? Well maybe I have 500 tons of binaries that depend on this old pack... Isn't it possible? What if I do need that old package still on my station? Why I do need to "upgrade" before rebuilding? Why do i need to downlod _both_ the source and the binaries of one and the same package? What if I don't note that versions/builds differ? In this particular case that is what happens... ImageMagick-5.2.3-1 requires only "ImageMagick-devel"... So no wonder if compiles/builds will fail. Or we get some schizo binaries and get wondering about what went wrong... What if I don't need this library on this machine? Why I should install it? Maybe I need to build it for something else. To study the stuff, to install on other machine, to make a later install... No, you first must install it... Doesn't this slightly remind something to you? Ektanoor
