Bug#707851: debian-policy: soften the wording recommending menu files
On Saturday 11 May 2013 13:36:36 Russ Allbery wrote:
> I think I agree with this move, but I'd really like it to come in
> conjunction with adding a recommendation to include a desktop file, since
> that's what most of the desktop environments actually use. That way, we
> don't lose functionality.
>
> Would you be willing to take a first stab at writing something like that?
Something like:
--- a/policy.sgml
+++ b/policy.sgml
@@ -7984,20 +7984,18 @@ Reloading <var>description</var> configuration...done.
<sect id="menus">
<heading>Menus</heading>
- <p>
- The Debian <tt>menu</tt> package provides a standard
- interface between packages providing applications and
- <em>menu programs</em> (either X window managers or
- text-based menu programs such as <prgn>pdmenu</prgn>).
+ <p>Applications that belongs in the menu of a desktop environment
+ or a window manager should provide desktop files for integrating
+ with the menus.
</p>
- <p>
- All packages that provide applications that need not be
- passed any special command line arguments for normal
- operation should register a menu entry for those
- applications, so that users of the <tt>menu</tt> package
- will automatically get menu entries in their window
- managers, as well in shells like <tt>pdmenu</tt>.
+ <p>For desktop files, see the Desktop Menu Specification available at
+ <tt><url name="http://standards.freedesktop.org/menu-spec/latest/"
+ id="http://standards.freedesktop.org/menu-spec/latest/"/></tt>
+ </p>
+
+ <p>Packages can, to be compatible with legacy debian additions
+ to some legacy window managers, provide a menu file.
</p>
<p>
/Sune
--
Man, how to telnet from the tool?
You cannot receive the hardware, so that from Word you neither must send to a
9-inch SCSI terminale to a graphic connection, nor need to load from the BIOS
jumper for pinging a RW SMTP BIOS over a LCD processor of a IP hard disk of
the bus on the sendmail.
Reply to: