> especially when the full burden of automatability is placed on the
> (small number of) integrators vs. the (larger number of) package
> maintainers.

but there's not reason for it to be that way. Addressing that issue is
cleaner and more constructive than abandoning smooth upgradability.

Many package systems put the burden on maintainers (not release
managers) via install/remove scripts attached to the packages - why
not do that in MC? As you know I submitted a quick first-pass
implementation of MC install/remove scripts months ago (and have a
better one somewhere if anyone cares) and you integrated it into some
line of MC, so there isn't even a technical problem to solve there.

Couldn't Daniel's Trait-script be attached there? So again - where is
the actual technical problem that cannot be solved via such fairly
simple solutions and which requires dumping smooth upgradability?

Michal