unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: "Feng Shu" <tumashu@163.com>
To: guix <guix-devel@gnu.org>
Cc: Feng Shu <tumashu@163.com>
Subject: Re: Suggest A debian-style menu system for guix
Date: Mon, 24 Apr 2017 18:28:44 +0800	[thread overview]
Message-ID: <877f2af6ar.fsf@163.com> (raw)
In-Reply-To: <20170424094807.grk3vhgismvb3aku@abyayala> (ng0@pragmatique.xyz's message of "Mon, 24 Apr 2017 09:48:07 +0000")

ng0 <ng0@pragmatique.xyz> writes:

> tumashu transcribed 1.0K bytes:
>> Debian menu system (https://www.debian.org/doc/packaging-manuals/menu.html/ch3.html) is a very useful tool,
>> is it possible develop a similar tool for guix?
>
> Could you explain what this exactly does?
>
> The manual page only documents the insides, not the description.

The below comment is from debian menu introduction.  if a package have a
debian menu file,  all window-manager's menu in debian will show this
package menu.

#+BEGIN_COMMENT
 Before the advent of update-menus, when the sysadmin installed a package onto a Debian system, they would need to edit various window manager config files to make the new program show up on, for example, fvwm's menus. The menus could easily become out of sync with what programs were actually available, with some menu items that didn't work, and other programs that lacked a menu entry. update-menus and Debian's menu package aim to solve this problem.

update-menus automatically generates menus of installed programs for window managers and other menu programs. It should be run whenever a menu file or menu-method file is changed. update-menus will be ran automatically when Debian packages that contain menu files are installed or removed from the system. Users themselves can add/delete menu items, and should then run update-menus as that user, thus creating window-manager startup files that are used in preference to the systemwide files. 
#+END_COMMENT

-- 

  reply	other threads:[~2017-04-24 10:28 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-04-24  8:46 Suggest A debian-style menu system for guix tumashu
2017-04-24  9:48 ` ng0
2017-04-24 10:28   ` Feng Shu [this message]
2017-04-24 12:15     ` William Seddon
2017-04-24 12:22     ` ng0
2017-04-24 12:48       ` Feng Shu
2017-04-24 13:38         ` Hartmut Goebel
2017-05-01 14:25         ` Adonay Felipe Nogueira
2017-05-02  6:07           ` Chris Marusich
2017-05-02  9:45             ` XDG standard desktop entries - desktop-file-utils and gtk, and KDE: mechanism of desktop database generation in profiles Danny Milosavljevic
2017-05-08  0:35               ` Chris Marusich
2017-05-28  7:20                 ` Danny Milosavljevic
2017-05-02 11:34             ` Suggest A debian-style menu system for guix Adonay Felipe Nogueira

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://guix.gnu.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=877f2af6ar.fsf@163.com \
    --to=tumashu@163.com \
    --cc=guix-devel@gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/guix.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).