Henning Makholm wrote: > Evidently, so that's not what is proposed. The proposal is to enhance > update-menus such that it knows how to parse .desktop files and feed > the information from them transparently to menu methods that expect > the Debian native format. Then debian-native menu systems would give > the same user experience independently of which packages had > transitioned to the .desktop format. The head of this thread is about someone asking several developers to drop .desktop files into their packages right now. Matthias Urlichs <smurf@smurf.noris.de> wrote: > AKL. Mantas Kriauciunas wrote: > >> Herbert Xu: "Please discuss this on debian-devel before filing further >> bugs." > > IMHO, there's no need to discuss this to death -- .desktop files make > sense, therefore packages should supply them. There's no sane way to ask > maintainers to do so except to file bugs, therefore bugs should be filed, > and that's all there is to it. There are bugs in the BTS about this, for example #219304. This is being gone about ass-backwards. > > You speak of a transition, but I see no transition plan here. > > What do you expect from a "transition plan" then? > > Step 1a: Update menu infrastructure such that packages can transparently > supply either .desktop files or Debian menu files. > > Step 1b: At the same time, update menu infrastructure such that WM > packages providing menu methods can opt to receive package data in > .desktop format (autotranslated from Debian menu files if necessary). > > Step 2: Packagers can now chose to supply .desktop files instead of > the Debian format, with a versioned dependency on menu. > > Step 3: After a stable version with the updated infrastructure has > been released, the Debian menufile format can be deprecated > (should not happen before, because it would make backports > harder). > > Step 4: When all (or most) menu methods have been converted to > reading .desktop files, policy can be amended along the lines of > "*must* provide a .desktop file rather than the old > Debian-specific menu format". > > Stem 5: Compatibility code for the old format in the menu > infrastructure will be kept until it gets too much of a burden > to maintain it. Apparently some people are trying to start at something not unlike your step 2, without changing menu first. -- see shy jo
Attachment:
signature.asc
Description: Digital signature