2009/1/19 Douglas Philips <[email protected]>
> On or about 2009 Jan 19, at 2:00 AM, Peer Sommerlund indited:
> > I have a similar setup. At first I did the full install, and did get
> > into trouble trying to debug interactions between the two kinds of
> > installation. Now, I avoid installing the from-source-version in
> > explorer and this gives a stable system. For testing, the hgtk
> > command gives access to all dialogs (I think) from the command line.
> >
> > You should do all steps, except "python tortoisehg.py" which
> > installs the explorer extensions - this means just do step 1 and 2
> > of the source installation guide [1]. The only tricky part is
> > mercurial installation. [2]
> >
> > [1] http://tortoisehg.sourceforge.net/InstallingTortoiseHg.html
> > [2] http://www.selenic.com/mercurial/wiki/index.cgi/WindowsInstall
>
> Well, as they say, "That first step is a doozy."
> I have ActiveState Python already installed.
> The rest, I cannot install since, again, I only have one machine, and
> I have to be sure that my Python setup is the same as everyone elses
> setup on my team. "Oh, but PyGTK won't hurt." Sorry, I've been doing
> software for 30 years and far far too often folks forget about some
> extra library or search path change or dependency or ... and there is
> no way I am spending/wasting any time chasing that stuff down, I have
> spent far too much time doing that already in my career.
>
So true. I think we have all had these walks in the dark. No reason to do
more than necessary of this.
I must say that the python environment confuses me from time to time, and
the lib/site-packages is not always a blessing.
I got some help from http://pypi.python.org/pypi/virtualenv
<http://pypi.python.org/pypi/virtualenv>during
the hg 1.0 to 1.1 transition where I had to have two different working
environments.
> Look, having a installer means TortoiseHG's Python environment,
> Mercurial setup, etc. are all --isolated-- from my main working Python
> install.
> Really, building an installer --should-- be easy.
I completely agree.
>
> I'm talked out on this. I would love to be able to contribute, but my
> circumstances are such that it won't happen without a pushbutton
> installer build.
>
Well, you are already contributing: Ideas, bugreports, etc.
In the situation you describe an installer wouldn't make a difference. You
would still have to go through the source installation steps to be able to
write code.
Regards,
Peer
------------------------------------------------------------------------------
This SF.net email is sponsored by:
SourcForge Community
SourceForge wants to tell your story.
http://p.sf.net/sfu/sf-spreadtheword
_______________________________________________
Tortoisehg-discuss mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/tortoisehg-discuss
