Forcible Deactivation
Posted: 07 Oct 2014, 00:10
Keep on meeting up with this problem of a module not being able to be deactivated, because of being required somewhere else, a case in poiint being kdelibs, where Kate needed a library which could only be found in kdelibs. Sometimes when testing for module dependency, the module, I presume, provides something which a library in nepomuk or soprano or kdelibs needs. However this library is irrelevant for installed programs on system. Disengagement of module should have no repercussions.
Another problem is where two modules are dependent on each other, but cannot deactivate both, because of interdependency. Any way possible to deactivate both simultaneously?
Is there a way to forcibly deactivate?
Another problem is where two modules are dependent on each other, but cannot deactivate both, because of interdependency. Any way possible to deactivate both simultaneously?
Is there a way to forcibly deactivate?