|
我今天下载了一个KDE窗口装设,结果MAKE INSTALL完了却发现控制中心里没有刚才安装的主题。然后上网找原因,果然如此,大家请看:
Mandrake Breakage
Mandrake uses a non-standard directory structure that breaks KDE software installation when compiling from source. Specifically, it uses a non-standard directory for the configuration files that control what shows up in the KDE Control Center, in the menus, and mimetypes. That means that not only my software, but any third party KDE software you install from source will be missing their entries in the menu, file associations, and any Control Center modules they may install.
This problem has existed for several Mandrake versions and they seem not to care about fixing it despite the fact that by default no software compiled from source will have menu or Control Center entries. They seem to think you should only use the RPMs they provide ;-) Okay, but then when I asked them to provide RPMs for my software they said they didn't have the time >:/
Some of my stuff has appeared in Mandrake Cooker, and other stuff is available as unofficial packages. Otherwise you may be able to use their menu tool to reset the menu structure to the correct standard structure, (I don't know about this - I don't use Mandrake). Make sure to let Mandrake know that you want to be able to compile KDE apps from source and have everything work out of the box - including menus entries and the Control Center!
Liquid will not work correctly because of Mandrake's broken menus. You will not get the Control Center module required for configuring it.
Update (01/19/2003): Some people have claimed that Mandrakesoft works fine with other KDE software installed from source. That is not true. You may be able to *run* the software but any new KDE Control Center modules, servicetypes, and mimetypes will not work. They also are not installed in the menus because of Mandrakesoft's nonstandard menu structure. This applies to any software that uses the standard KDE autoconf/automake, which is virtually everything.
-=-=-=-=-=-=-=-=-=-谁能把这个问题搞定?-=-=-=-=-=-=-=-=-=-=-=-=-=- |
|