On Thu, Jul 06, 2017 at 01:32:00PM -0000, Julian Andres Klode wrote:
> I think automatic updating on old caches is not really the best idea,
> because it will always happen when you expect it the least. Or maybe you
> do in fact want the old one.
From the perspective of users, I absolutely disagree. Users always want
the latest. Users expect a download, so hitting the archive index should
never be a problem.
A user not wanting the latest is actually being a developer.
> Or maybe you do in fact want the old one.
Developers might, sure. Developers would have to override using a CLI
option or set some global configuration to override. But I think the way
forward for the "apt" CLI is to be user-centric. This is the entire
point of it, no?
The defaults can either be sensible for users, or for developers. This
is an example where I think it cannot be both. So what should "apt" be?
On Thu, Jul 06, 2017 at 01:32:00PM -0000, Julian Andres Klode wrote:
> I think automatic updating on old caches is not really the best idea,
> because it will always happen when you expect it the least. Or maybe you
> do in fact want the old one.
From the perspective of users, I absolutely disagree. Users always want
the latest. Users expect a download, so hitting the archive index should
never be a problem.
A user not wanting the latest is actually being a developer.
> Or maybe you do in fact want the old one.
Developers might, sure. Developers would have to override using a CLI
option or set some global configuration to override. But I think the way
forward for the "apt" CLI is to be user-centric. This is the entire
point of it, no?
The defaults can either be sensible for users, or for developers. This
is an example where I think it cannot be both. So what should "apt" be?