Hi, please note I'm not used to doing weird things in maintainer scripts, I might be naive in the next sentences.
Eugene V. Lyubimkin <jackyf.de...@gmail.com> (20/12/2009): > Yes, this is a solution, but cupt doesn't consider it by default, > because of reasons explained in [1], in short: new 'tex-common' > package may have maintainer scripts which may have some actions for > upgrades from older 'tex-common' versions, and they will not be > called in such a sequence. I think you don't really have to care about this. I think the maintainers scripts have to do the right thing: - either do whatever is needed if upgrading from an earlier version; - or behave as if it was a new installation, if the package got removed in the meanwhile. If there is some stuff left from a previous installation, meaningful to some upgrade path, that has to be detected by the maintainer scripts, even if that's not an upgrade, strictly speaking. So I guess the package manager should just be neutral, and either do an upgrade when possible, or remove-then-install when needed, and let the maintainer scripts do their jobs. I shall note again I might just be naive. Mraw, KiBi.
signature.asc
Description: Digital signature
