On Mon, 12 May 2008 17:06:17 +0200, Pierre Habouzit <[EMAIL PROTECTED]>
wrote:
On Fri, Mar 21, 2008 at 02:37:57PM +0000, Jiří Paleček wrote:
Package: cmake
Version: 2.4.8-1
Severity: important
Hello,
when installing cmake and emacs (at the same time), I got the following
error message
Setting up cmake (2.4.8-1) ...
ERROR: emacsen-common being used before being configured.
ERROR: This is likely a bug in the cmake package, which needs to
ERROR: add one of the appropriate dependencies.
No this is not an option for cmake to depends on emacsen, it would be
more than bloated. This isn't appropriate, and it wouldn't be
appropriate to have a separate cmake-mode just for two files either. The
emacs policy is broken, I won't do that.
Broken? Isn't that too strong a word?
This issue is an emacsen-common
technical limitation, and I assume dpkg triggers could resolve that in a
nice way, I'm totally open to update my cmake emacs integration, but not
to the cost of a dependency on emacs.
How about using
[ "$(dpkg-query -W -f='${Status}' emacsen-common 2>/dev/null | cut -d ' '
-f 3)" = "installed" ]
instead of
[ -x /usr/lib/emacsen-common/emacs-package-install ]
? Or swallowing the error from emacs-package-install? Just thoughts...
BTW there was once a discussion on -devel that resulted in consensus that
emacs doesn't need triggers. But the opinion might have changed since then.
OT BTW: why doesn't cmake 2.6 include ccmake? I haven't found any info on
that...
Regards
Jiri Palecek
--
Using Opera's revolutionary e-mail client: http://www.opera.com/mail/
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
