Remy Blank escribió:
Abraham Marín Pérez wrote:
That is indeed true, however, it will always be better keeping things
right than breaking and fixing as a rule, don't you think?
The thing is, you will *have to* break things at some point anyway. In
your case, it will be when you decide to update LIB (because you want to
have the new features, or because another package needs the new
version). Between the LIB update and the APP recompilation, APP will be
broken.
Even worse, if you don't know that the LIB update will break APP, you
might not notice immediately that APP is broken, or you might only get
some strange results from APP. That's where revdep-rebuild steps in: it
can tell you that APP is broken, and what's needed to fix it. So you're
better off running it consistently after your regular updates.
I'm not talking about not needing revdep-rebuild nor saying non-deep
updates would prevent breaking dependencies, I just said that non-deep
updates will *reduce* the amount of packages that need to be rebuilt. I
systematically run revdep-rebuild after every update world (in fact,
it's all in a script which performs update world, revdep-rebuild and
update-eix), but I'd rather have it reinstalling 2 packages than 20.
That's all.
Abraham
--
[EMAIL PROTECTED] mailing list
