On or about 2009 Jan 19, at 11:52 PM, TK Soh indited: >> Really, building an installer --should-- be easy. > > It should. But it isn't (and we are working on it)
I am glad about that, it will remove the friction from a lot of places. > Just to understand and hopefully help us improve. How is not able to > build the installer, easily or not, stopping you from contributing > patches? > > True, you need the to setup the development environment in order to > build the installer, but to hack TortoiseHg, you need, and only need, > the development environment. As I mentioned in a previous message, I have only one machine that I can hack TortoiseHg on and do my $$payingjob on, so I cannot install PyGTK or Pywin32. I had hoped that merely having those pieces on my system (but not installed into Python), would be sufficient for me to build the installer. So my (hypothetical) workflow would be to make changes in a sandbox, build the installer, install it, and then test the changes. Not as spiffy as the dev team working from source, but acceptable given the other constraints that I have. But it sounds like that wouldn't work anyway... oh well. --Doug ------------------------------------------------------------------------------ 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
