On Wed, Feb 06, 2002 at 04:41:10PM +0100, Julio Merino wrote:

> Yeah, the problem is that changes between old orbit and new one are only
> some minor version numbers... I can't understand why it has recompiled
> everything depending on orbit. Usually, minimal changes do not affect
> to other programs when running in a system wth dynamic libraries.

Well, first of all, make update is quite brutal, it does not consider
if a package really is no longer needed, but it's sane. What could be
biting you is explicit build or run dependancies from the new package
(like you have 2.10 installed and a package really requires >= 2.11).
In fact I'm currently working on an extension on the pkg_chk package
which should take care of it... once I can find the bug in what I have
now...

> So, my question... can I avoid this? Lets say, upgrading a package that
> has changed only its minor number without updating everything else?

Yes, but you need thorough investigation for that :) btw, a package like
pkg_chk still can help you because it compares the pkgsrc tree against the
installed versions (try pkg_chk -i :). If a package requires a certain
package (like the above 2.10 / 2.11) then you can't avoid it though.

hth, Martin Weber