Written by bloodniece the 9 Jun 09 at 18:55.

A simple shell script can be linked to in the menu that removes Mono and all Mono dependent apps from the system. Maybe add the option to NOT install Mono-based apps at the installer level of after a fresh install.

A simple shell script can be linked to in the menu that removes Mono and all Mono dependent apps from the system. Maybe add the option to NOT install Mono-based apps at the installer level of after a fresh install.

Written by gazilla the 11 Jun 09 at 02:17.

Think of a logjam in a river. One log gets stuck and many others get jammed up behind it. What is required in the package management system is the ability to lock any given package name to any given status or version.

Doing this would cause the install or upgrade of packages that depend on the install or upgrade of the locked package to fail (intentionally). This is useful for two main reasons.

One, it satisfies the desire of the (name-your-favourite-evil-package)-haters to never allow the package to be installed. So I could (e.g) lock libmono* to "never install". Installs of f-spot and tomboy would then fail. (GO gnote!).

Two, it allows for packages to be version locked. For example, I may wish to lock PHP at the current 5.2.6 as some new behaviour in 5.3.x is going break one of my systems badly. (Not a REAL problem, just an example)

Of course, there would have to be some way to manage the locked packages. A GUI showing the packages you have locked with a list of what has been "jammed up" behind.

Think of a logjam in a river. One log gets stuck and many others get jammed up behind it. What is required in the package management system is the ability to lock any given package name to any given status or version. Doing this would cause the install or upgrade of packages that depend on the install or upgrade of the locked package to fail (intentionally). This is useful for two main reasons. One, it satisfies the desire of the (name-your-favourite-evil-package)-haters to never allow the package to be installed. So I could (e.g) lock libmono* to "never install". Installs of f-spot and tomboy would then fail. (GO gnote!). Two, it allows for packages to be version locked. For example, I may wish to lock PHP at the current 5.2.6 as some new behaviour in 5.3.x is going break one of my systems badly. (Not a REAL problem, just an example) Of course, there would have to be some way to manage the locked packages. A GUI showing the packages you have locked with a list of what has been "jammed up" behind.