Re: Intent package mule2 and custom-mule (Important for emacs (lisp) package maintainers)

[David Benson <daveb@idealab.com>]

> > This is policy violation, isn't it?
> > 
> > >From Debian Policy Manual
> > | 5.8 Programs for the X Window System
> > |
> > | Some programs can be configured with or without support for the X Window
> > | System. Typically, binaries produced with support for X will need the X
> > | shared libraries to run.
> > | 
> > | Such programs should be configured with X support, and should declare a
> > | dependency on xlib6g (which contains X shared libraries). Users who wish to
> > | use the program can install just the relatively small xfree86-common and
> > | xlib6g packages, and do not need to install the whole of X.
> > | 
> > | Do not create two versions (one with X support and one without) of your
> > | package.
> 
> Then, is vim-tiny also a policy violation?

I sure hope not.  
I know of noone who actually uses the vim x interface,
even though I have quite a few friends who use vim.

But b/c of debian policy I'll have to
install X on all my servers.

In my opinion gvim should be put in a package gvim, largely
independant of vim.  (Maybe a vim-common is necessary)
Policy should be updated to allow separate packaging
of programs whose GUI is peripheral.

It smacks one of vim's four design goals (www.vim.org/deve.html)
right in the face:

    No GUI required 
        Vim is supposed to work on all available terminals -
        however simple. Vim's commands should be powerful enough
        to make a mouse superfluous.  However, Vim has support
        for GUI to allow menus and copy&paste via the mouse to
        accommodate casual users and those who are used to mice
        (eek! ;-). If you don't want to use Vim with a mouse then
        you can install it with the option "-gui" (ie "no GUI").

- Dave