On 30/09/13 01:34, Charles Plessy wrote:
Le Sun, Sep 29, 2013 at 10:01:50PM +0200, Daniel Pocock a écrit :
For those feeling lazy, I suppose we can just grab the .desktop file
generated under /var by update-menus and copy it into our packages? Or
is there a more elegant way to manage the
I've been trying to create menu items for postbooks and
postbooks-updater, for example:
http://anonscm.debian.org/gitweb/?p=collab-maint/postbooks-updater.git;a=blob;f=debian/menu;h=456d003f95312b27e3a1301057dd5b8dc3efca36;hb=86c8d75cc7297ba47b6398930c256d202011ab93
is a debian/menu file
On Sun, 2013-09-29 at 19:55 +0200, Daniel Pocock wrote:
I can see that update-menus is run during the dpkg install and I tried
running it again manually.
I can even find the .desktop file for Gnome after update-menus has run,
it looks OK
However, the item just doesn't appear in the menu,
On 29/09/13 20:09, Adam D. Barratt wrote:
On Sun, 2013-09-29 at 19:55 +0200, Daniel Pocock wrote:
I can see that update-menus is run during the dpkg install and I tried
running it again manually.
I can even find the .desktop file for Gnome after update-menus has run,
it looks OK
However,
On 29/09/13 21:01, Daniel Pocock wrote:
- Debian appears to have a perfectly good menu tool and it is not clear
why it has to be ditched.
Upstreams often ship desktop files; menu files are Debian-specific; and
if a GUI environment has Debian-specific infrastructure to display both,
it will
Le Sun, Sep 29, 2013 at 10:01:50PM +0200, Daniel Pocock a écrit :
For those feeling lazy, I suppose we can just grab the .desktop file
generated under /var by update-menus and copy it into our packages? Or
is there a more elegant way to manage the duplication with debhelper
support perhaps?
6 matches
Mail list logo
