Hi, On Mon, 26 Feb 2007, andreas.hanke@gmx-topmail.de wrote:
While I agree with many of your points, this argumentation is flawed. If libabc is not directly used (i.e. in the deplist without a relocation into it) then any API change in libabc can't break the application. If it can break the application then by definition it's not unused. Additionally, if it breaks the API, then probably some of the libraries directly depending on it, which are used by the application (otherwise the useless dep wouldn't exist), will break too. That breakage will occur no matter if the useless deps are removed or not.
Hence: removing the useless deps will not magically make API breakages go away.
What happens if libfreetype.so.6 becomes libfreetype.so.7 and is really not used? In such a case it can indeed break dependent packages unnecessarily.
Well, for libfreetype.so.6 to be in the deplist of application app, it had to be linked against some other library (let's say libbla.so), which itself links directly against libfreetype.so.6 and really uses it. If libfreetype.so.6 doesn't exist anymore then that library will break, no matter if app links against libfreetype.so.6 or not. As libbla.so really uses that library it's also no unneeded direct dependency, so you have to rebuild something anyway (libbla.so in this case). So, removing unneeded direct dependencies will not solve that problem at all. What it will do, though, is that less stuff has to be rebuilt. Ciao, Michael. --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-packaging+help@opensuse.org