On Tue, Jul 29, 2008 at 9:37 AM, Georg <[EMAIL PROTECTED]> wrote: > Oops, should have gone to the list. > > ---------- Forwarded message ---------- > From: Georg <[EMAIL PROTECTED]> > Date: 2008/7/29 > Subject: Re: [Tortoisehg-discuss] my Python hook is not found any more in > 0.4rc3, GUI > To: TK Soh <[EMAIL PROTECTED]> > > > Yes, I copied it into library.zip/hgext. That was the only way I found to > add something to the Python path of Mercurial on Windows. I posted another > question on the "proper way" to add an extension (well, it's not really an > extension, just a hook) a while ago, but didn't get other advice.
There have got to be a better way to do this. I am surprised the Mercurial folks didn't give anything helpful on this topic. I imagine it should be something like the way 3rd party extensions are handled. But maybe not. Personally, I have no experience with hook at all. > Adding into library.zip is really easy using Windows explorer, just drag and > drop. The drawback is I have to do this again after every reinstall/upgrade > of TortoiseHg. Interesting :-) > The hook is enabled like this in Mercurial.ini: > > [hooks] > # create symlinks after hg update > update.msc = python:hgext.msc.hook > # remove old symlinks before hg update > pre-update.msc = python:hgext.msc.hook > # enforce MSC branch name policy before commit > pre-commit.msc = python:hgext.msc.hook Thanks. Give me sometime to think about this. ------------------------------------------------------------------------- This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/ _______________________________________________ Tortoisehg-discuss mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/tortoisehg-discuss
