Bug#427829: qct: Removing causes Mercurial errors

[Thomas Arendsen Hein]

* Vincent Danjean <vdanjean.ml at free.fr> [20070725 14:21]:
>   The problem occurs when qct package is removed but not purged.
> In this case, the conffile keep here. So mercurial try to load
> qct but cannot because the extension is not here anymore.
>   I cannot remove /etc/mercurial/hgrc.d/qct.rc on 'remove' operation
> because this will go against debian policy.
> 
> 
>   One solution I see would be to extend the syntax of extension loading
> in mercurial so that it would be possible to try to load the extension
> if present but not to fail if the extension is not present.
>   Note that this cannot be the default: if a user requires a extension,
> it is better to fail immediately if the extension is not here.

I'd like to have a syntax for defining optional extensions, too, to
support one hgrc being used with different versions of Mercurial.

Specifying more than one location to try might be helpful, too, for
renamed extensions.

What about borrwing shell syntax '||'? The '!' can aleeady be used
to disable an extension.

hgext.foo = || !
bar = /path/to/bar || /path/to/bar.py || !

Regards,
Thomas

-- 
thomas at intevation.de - http://intevation.de/~thomas/ - OpenPGP key: 0x5816791A
Intevation GmbH, Osnabrueck - Register: Amtsgericht Osnabrueck, HR B 18998
Geschaeftsfuehrer: Frank Koormann, Bernhard Reiter, Dr. Jan-Oliver Wagner