On 5 Mar 2002, Guillaume Cottenceau wrote: > > > > $ rpm -qa | grep libwmf0.2 > > > > > > > > libwmf0.2_1-0.2.1-1mdk > > > > libwmf0.2_2-0.2.2-1mdk > > > > > > That's the point of the "new lib policy". > > > > So we just get more and more and more libs forever? Is this why I have > > Yes, we have decided that this problem is far better than > previous situation where upgrade basically broke things because > of missing/conflicting libraries. > > > to keep manually uninstalling libfoo18-devel packages whenever I need to > > -Uvh libfoo19-devel? Surely something more elegant can be conceived.
Yeah, some time ago I was thinking what you are thinking now, and even created packages that worked like what you have described. But later I discovered that, this will usually break things in subtle way. Let's consider gal and gtkhtml as example; usually gtkhtml needs to be built against some specific version of gal, and if non-matching devel packages are mixed (e.g. by upgrading libgal-devel without upgrading libgtkhtml-devel), this usually results in a broken libgtkhtml-devel. Abel
