You are not logged in.
Pages: 1
Hello,
I was playing around with the xorg-server 1.7.0. And perhaps someone can give me some insights about the dependency problem.
When compiling the xorg-server it complained that the xextproto-package was to old.
The dependency list for the xextproto-package is as follows:
xorg-server -> libxv -> libxext -> xextproto
My problem is the following: If I want to upgrade xorg-server I have to recompile libxv too, because it has xextrproto inherited through libxext as dependency. What you can't see from the list is if libxv really has to be recompiled (is directly dependant on xextproto) or if you can leave the package untouched. In my opinion this doesn't make a lot of sense, because in that case one would have to recompile a lot of packages.
Edit: Ok, I think I understood now what the makedepends is good for. If I understand it correctly then the packages listed in makedepends are direct dependencies. This means one has to recompile the package either if one of the package in depends or makedepends changes.
According to the wiki makedepends is "An array of package names that must be installed to build the software but unnecessary for using the software after installation. You can specify the minimum version dependency of the packages in the same format as the depends array." Ok, I just checked the xorg-server PKBUILD and xextproto is listed as a makedepends.
Edit2: How about adding (if it's possible) an entry about makedependencies just like the dependencies on the package site?
This leads me to the next question. I've read somewhere about so called .so-name bumps. Can anybody explain me what these are and how they fit into this context.
ABI and API changes are also buzzing in my head. How to these catchword fit into this context (do they?)?
As as summarize: in which cases do I have to recompile packages?
I would be very thankful if someone could give me some insights here.
Last edited by BertiBoeller (2009-10-12 07:18:18)
Offline
Pages: 1