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

Martin Geisler mg at lazybytes.net
Mon Jun 29 03:37:13 CDT 2009


Cédric Duval <cedricduval at free.fr> writes:

> # HG changeset patch
> # User Cédric Duval <cedricduval at free.fr>
> # Date 1246176984 -7200
> # Node ID a61ea0b22a3f6f3a0a6bb209b58a64efeed22c01
> # Parent  835a51e63c5b0e4eee4f95fcbbdaf4476629a621
> extensions: extract descriptions at build time
>
> This series of two changesets fixes issue1708, by pre-processing
> extensions descriptions at build time, rather than trying to extract
> them at runtime.
>
> This frees us from the quirks of the various packaging schemes, e.g.
> on win32 (with py2exe) extensions are shipped inside a library.zip
> archive stripped from all the py files.

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.

Perhaps this is okay, but it does make things a bit less transparent
compared to our current solution.

-- 
Martin Geisler

VIFF (Virtual Ideal Functionality Framework) brings easy and efficient
SMPC (Secure Multiparty Computation) to Python. See: http://viff.dk/.



More information about the Mercurial-devel mailing list