[PATCH 1 of 2] extensions: extract descriptions at build time

[Dan Villiom Podlaski Christiansen]

On 29/06/2009, at 13.56, Cedric Duval wrote:

> Martin Geisler wrote:
>> With your proposal users cannot just install a new extension into  
>> their
>> hgext folder and expect it to show up in the 'help extensions' list.
>
> Not without a 'make all' or 'make local', yes, if we're talking about
> hgext in a source tree. But that seems reasonable for the kind of
> persons who'd do that.

I suspect Martin was referring to third-party extensions, such as  
hgsubversion. Allowing the extensions topic to list and describe third  
party extensions too would make it much more valuable, in my opinion.  
Especially in situations where system administrators or package  
managers install other extensions.

Another thing, though, that I'd consider useful, is to be able to show  
help for uninstalled extensions. I assume your patches allow this  
possible for bundled extensions? I wrote up a small patch to do it for  
other extensions as well; basically, I just changed the disabled()  
method to optionally return the full description, and used that as a  
another final fallback for finding a help page.

The patch is attached below.

--

Dan Villiom Podlaski Christiansen
danchr at gmail.com

-------------- next part --------------
A non-text attachment was scrubbed...
Name: disabled-extensions-help.diff
Type: application/octet-stream
Size: 3279 bytes
Desc: not available
Url : http://selenic.com/pipermail/mercurial-devel/attachments/20090629/dc2c9a24/attachment.obj 
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 1943 bytes
Desc: not available
Url : http://selenic.com/pipermail/mercurial-devel/attachments/20090629/dc2c9a24/attachment.bin