On Wed, May 06, 1998 at 10:01:43AM -0700, John W. Jones wrote:
[...]
If package-get-update-all is (trivially) changed to not go after
dependent packages, then it acts as expected for both user A and user
B. It works for user A because he has dependent packages, and if
package-get-base shows a newer version of one of those has come out,
package-get-update-all will still get that newer version.
But this will kill A is the update happens to need a new package he
does not have.
Remeber A's behaviour will be standard one. B is the smart one. So he
can be required to set a particular "don't go after dependencies
automatically" flag, which will act consistently for package-get-*-all
Principle of least astonishment is only valid if it does not preclude
the pattern of use encoutered the most often.
OG.