On Sat, 17 Apr 2010 23:07:48 -0700, Carl Worth <cwo...
> On Sat, 17 Apr 2010 21:37:28 +0200, Xavier Maillard <x...
> > Currently, notmuch package embeds both vim and GNU Emacs client
> > interfaces. I think we are wrong doing so.
> Could you explain what you perceive as the problem here?
> So far, the package is really just tracking the upstream approach. And
> the upstream approach is that the notmuch command-line interface isn't
> useful without at least *some* higher-level interface. So everything
> that exists so far is bundled.
Actually, today, package is just suggesting to have emacs or vim
installed. You just told notmuch cli is not useful without at
least some higher-level interface -i.e. emacs or vim
currently. If that's the case, there is either a need to change
'Suggests' into something more "mandatory" or you need to package
your higher-level interfaces into their own specific package with
a Depends on notmuch-common or something like that.
Today, it is totally unclear for a new user to know that notmuch
has an interface for Emacs or Vim.
Worst, I am not sure that, as it is handled today, the package is
correct: what if somebody installs notmuch without either vim or
emacs (or both) ? How will the elisp files be processed when no
emacs installation is present ?
I hope I have been clear here. If not, I will try to explain it
better again (english is not my tongue).
To UNSUBSCRIBE, email to debian-bugs-dist-REQU...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org