Package: mercurial
Version: 0.9.4-1
Severity: normal
File: /etc/mercurial/hgrc.d/hgext.rc
Currently,
- by default, /etc/mercurial/hgrc.d/hgext.rc loads several extensions;
- a user whose $HOME is shared across multiple (heterogeneous) hosts
is likely to want to enable these extensions explicitly in her
~/.hgrc;
- loading an extension twice under a different "name" causes hg to
complain to stderr (because the bindings shadow themselves):
$ grep mq ~/.hgrc /etc/mercurial/hgrc.d/hgext.rc
/home/twb/.hgrc:hgext.mq=
/etc/mercurial/hgrc.d/hgext.rc:hgext/mq=
$ hg help >/dev/null
extension 'hgext/mq' overrides commands: qheader qnew ^qpop qrestore
qapplied qguard qclone ^strip qgoto qprev qunapplied ^qrefresh qtop ^qdiff
qseries qcommit|qci qfold qnext qdelete|qremove|qrm ^qimport qselect ^qpush
^qinit qrename|qmv qsave
$
- mercurial.el includes this in the modeline, i.e. instead of
(Fundamental Hg:0)
one gets
(Fundamental Hg:module hgext/mq overrides qheader+module hgext/mq
overrides qnew+module hgext/mq overrides ^qpop+modul
This situation is undesirable. I see a number of potential solutions:
- user removes offending entries from hgext.rc. This is not feasible
because it requires root access.
- user removes offending entries from ~/.hgrc, then copies hgext.rc to
every other systems (e.g. BSD, OS X) on she uses. This is not
feasible because it requires root access.
- Debian maintainer notes in README.Debian that putting foo= or
hgext.foo= in ~/.hgrc causes problems, and users SHOULD use
hgext/foo= instead. User follows instructions, and we all hope that
no other distribution uses the hgext.foo= notation in its site-wide
rc file.
- Debian maintainer removes hgext.rc, so extensions are off by default
under Debian.
- Debian/upstream modifies mercurial.el to discard shadowing warnings.
This would solve the immediate issue, but of course anyone running
hg(1) directly on the command line would still see obnoxious
warnings on stderr.
- Debian/upstream modifies hg so that it understands that foo,
hgext/foo and hgext.foo are the same extension, and not to emit a
warning.
-- System Information:
Debian Release: lenny/sid
APT prefers unstable
APT policy: (990, 'unstable')
Architecture: amd64 (x86_64)
Kernel: Linux 2.6.22-2-amd64 (SMP w/1 CPU core)
Locale: LANG=en_AU.utf8, LC_CTYPE=en_AU.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Versions of packages mercurial depends on:
ii libc6 2.6.1-5 GNU C Library: Shared libraries
ii python 2.4.4-6 An interactive high-level object-o
ii python-support 0.7.4 automated rebuilding support for p
ii python2.5 2.5.1-5 An interactive high-level object-o
Versions of packages mercurial recommends:
ii rcs 5.7-20 The GNU Revision Control System
ii tk8.4 [wish] 8.4.16-1 Tk toolkit for Tcl and X11, v8.4 -
-- no debconf information
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
