IndexError: list index out of range

[Vincent Danjean]

Matt Mackall wrote:
> On Tue, 2008-08-26 at 19:29 +0200, Vincent Danjean wrote:
>> Matt Mackall wrote:
>>> The hgweb problem is just bizarre. Mercurial's fairly popular main repo
>>> is served off a virtual server on a loaded box in my basement using slow
>>> CGI over DSL, and the load from Mercurial is negligible. He's probably
>>> got Pygments turned on by the silly Debian packaging.
>> Can you tell me what should be changed in the Debian packaging ?
>>
>> Are you saying that turning off all extensions when installing mercurial
>> would be better ?
> 
> YES!
> 
> Extensions provide *non-standard* functionality that may be unsafe,
> slow, fragile, underdocumented, undersupported, or even just plain
> discouraged (like keywords). If you want this non-standard
> functionality, you should have to go through a manual step to enable it.

Opening a bug with these arguments would have made me react quicker...
Note that I tried to enable by default only extension that add features
without modifying the plain behavior of mercurial. This means that extensions
such as keywords, win32text, ... have *never* been enabled by default in any
Debian package.
  Another strong argument I read in this thread is the fact that a extension
enabled system-wide cannot be disabled by a user. I thing that this is a
really good reason not to enable any extension by default in the debian package.

Now, I've a few questions/remarks for comments:
- the last point makes me think that extensions that are available on separate
  packages (such as qct) should not be enabled by default at install time, too.
  This means that someone willing to use this extension will have to install
  the package AND configure it manually
- the current Debian package installs mergetools.rc in the system-wide config
  directory (/etc/mercurial/hgrc.d)
  Is it a good thing ? Can the user overwrite any information that there is in
  this file without being root ?

  Regards,
    Vincent

PS: about the current package, it is too late to change the default configuration
for the next Debian release (lenny): the release managers will not accept such changes.
[the 1.0.2 release has also be rejected by the release managers]
After the release, I will package the 1.0.2 release with the changes in the configuration
discussed here (and make a backport for lenny)