/usr/share/mono/MonoGetAssemblyName.exe is used as part of the package installation process to register a package in the GAC. This app is linked against libmono-corlib1.0-cil, but doesn't depend on it. Without that app working, the manifest file which is used by the purge process (/usr/share/cli-common/packages.d/*.mono) is incorrect, and therefore doesn't lead to package removal (i.e. when the "gacutil" command is executed to run the remove, instead of getting a list of assemblies to remove (e.g. "Mono.Addins, Version=0.4.0.0, Culture=neutral, PublicKeyToken=0738eb9f132ed756"), it gets "The assembly mscorlib.dll was not found or could not be loaded."
This is too late to fix in Jaunty, but will be fixed in Karmic. For now, if you've purged all of Mono, then it's safe to delete /usr/lib/mono/gac
Okay, bug tracked down.
/usr/share/ mono/MonoGetAss emblyName. exe is used as part of the package installation process to register a package in the GAC. This app is linked against libmono- corlib1. 0-cil, but doesn't depend on it. Without that app working, the manifest file which is used by the purge process (/usr/share/ cli-common/ packages. d/*.mono) is incorrect, and therefore doesn't lead to package removal (i.e. when the "gacutil" command is executed to run the remove, instead of getting a list of assemblies to remove (e.g. "Mono.Addins, Version=0.4.0.0, Culture=neutral, PublicKeyToken= 0738eb9f132ed75 6"), it gets "The assembly mscorlib.dll was not found or could not be loaded."
This is too late to fix in Jaunty, but will be fixed in Karmic. For now, if you've purged all of Mono, then it's safe to delete /usr/lib/mono/gac