On 28.09.2008, at 19:01, Keith Hodges wrote:
Now, the code may work perfectly fine, and Keith's done a lot of work, but it's just not community friendly code. A package should have a clear responsibility, few dependencies, not too many extensions, no overrides if at all possible, and must install and uninstall cleanly without hosing my system. If it doesn't meet those criteria, I don't consider it safe to even experiment with.
Ramon Leon http://onsmalltalk.com
If it uses overrides, the MC1.5 should be able to uninstall it. However MC1.5 probably depends upon it. So you are probably stuck there.
keep in mind that unsinstall can not work in gereral... overrides are evil. So just think you installed some packate that has an override. Now you install a second, that overrides again. Ups, broken. So we change the new override to take into account the change done in the first. Now when de-installing the first package, what should happen?
Kernel-Extensions are not supposed to be removed, they are supposed to be integrated into the main image. We have two ways of doing this.
We are slowly breaking it down into bug fixes on mantis,
considering that mantis now has >1000 open entries... Marcus -- Marcus Denker -- denker@iam.unibe.ch http://www.iam.unibe.ch/~denker