Package: debian-policy Rationalle:
KDE uses it's menu files to let the system know alot of different information about a particular binary including how to launch it, what it's used for, mime types, etc. When we integrate the Debian menu within the KDE one we end up with duplicates. The information that Debian provides for a particular binary is the basics since the normal Deiban menu has no need for such extra information. KDE ends up seeing 2 different sets of information for the same binary and can (and usually does) gets confused. The easiest way around this is to use the menu system's features to not install a KDE menu entry when one already exists and thus avoiding the duplication altogether. Adding kderemove="y" to a Debian menu entry currently takes care of this and most KDE packages are already doing this. I'm not really sure where this should fit into policy but I assume it would go into the menu specific policy. I am also not good at the written word so if someone else can come up with better verbage that would be great. Proposal: "Packages which provide KDE menu entries must also add 'kderemove="y"' to their corresponding Debian menu entry. This allows the Debian menu system to ignore creating a KDE menu entry since one already exists." Transition: Most KDE based apps already use either 'kderemove="y"' or 'kderemove="1"' so transition is just a matter of getting everyone on the same page. Thanks, Ivan -- ---------------- Ivan E. Moore II [EMAIL PROTECTED] http://snowcrash.tdyc.com GPG KeyID=90BCE0DD GPG Fingerprint=F2FC 69FD 0DA0 4FB8 225E 27B6 7645 8141 90BC E0DD
