Couple packaging suggestions/questions

Stefano Zacchiroli zack at
Mon Aug 21 06:52:10 UTC 2006

On Thu, Aug 17, 2006 at 03:30:35PM -0400, James Vega wrote:
> Ah, I remembered the other item.  We currently ship a single
> gvim.desktop file and menu file in vim-gui-common.  This causes menu
> items to be present for non-existant executables if vim-gui-common is
> installed but a gui variant isn't installed.
> Lintian had been warning about this for a while, but I kept ignoring it
> because I thought it was a buggy check.  Should we change the packaging
> to ship a different .desktop and menu file for each gui variant?  The
> menu entries could then indicate which variant it is and would make it
> easier for the end user to choose which variant they want to use if
> multiple are installed.

I'm not sure about that: on one hand it would be a plus, though minor,
to let the user choose the variant directly from the menu. On the other
hand we already have a mechanism for choosing system-wide the preferred
variant for gvim, namely update-alternatives. So I would expect that we
also ship a .desktop for the "system default variant" of gvim, and then
we would be back at the starting issue ...

IMO the Recommends from vim-gui-common to the various variants is
enough. If people complain about that we could think at a
postinst/postrm hooks that disable the single .desktop file when no more
gui enabled variants are installed. Still, I don't think it is worth the


Stefano Zacchiroli -*- Computer Science PhD student @ Uny Bologna, Italy
zack@{,,} -%-
If there's any real truth it's that the entire multidimensional infinity
of the Universe is almost certainly being run by a bunch of maniacs. -!-
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: Digital signature
Url :

More information about the pkg-vim-maintainers mailing list