On Tue, Aug 19, 2008 at 5:34 PM, Peer Sommerlund <[EMAIL PROTECTED]> wrote: > > > 2008/8/19 TK Soh <[EMAIL PROTECTED]> >> >> On Sun, Mar 30, 2008 at 1:58 PM, TK Soh <[EMAIL PROTECTED]> wrote: >> > On Sat, Mar 29, 2008 at 11:58 PM, Peer Sommerlund >> > <[EMAIL PROTECTED]> wrote: >> >> Hi folks >> >> >> >> As you know I'm working on how allow Tortoises (-hg, -cvs, -svn, -darcs >> >> etc) >> >> to coexist by sharing overlay icons. This is a long journey, and has >> >> currently led to the TSVN team developing a nice component named >> >> TortoiseOverlay which allows one set of overlay icons to be used by >> >> everybody. >> > >> > I've yet to find time to try out your patches yet, so I can't make any >> > sensible comments. We should visit this issue in greater depth after >> > the release of 0.4. >> >> OK. 0.4 is released. Maybe we should talk about this again. Before we >> start, I wonder if your original post requires any update first. After >> all, it's been almost five months since your last post. > > Alas, as I'm very short on spare time, I have made no progress on this topic > since last time. Maybe I should look some more into it.
On a related topic, one thing I am not certain is whether we should do this now with the pywin32-based extensions, or to start working on the C++ version. There's quite a long list of TODO I have for 0.5. >>> ISSUE #1: Should we provide an .msi installer? > > I still believe we should try to make Inno Setup do what we want, possibly > by cooperating with the TCVS project and of course Mercurial, both of which > use Inno Setup. Certainly something we should evaluate. I did look at TCVS when creating the prototype for the C++ shell extensions, including the their Inno setup files. > I don't think an .msi installer is important. We can build an .msi simply by > wrapping the Inno Setup .exe - if we really want to. Windows has some > features for distributing .msi files that makes it attractive for system > administrators. Let's wait for some user requirements before switching > installer-tool. I am not familiar with the msi installer. It'd be nice we can wrapped Inno Setup's .exe into one like you said. One reason I think we will need an msi installer is to handle the installation of TortoiseOverlays.dll. I guess we have to bundle TortoiseOverlays in TortoiseHg's installer, and only install if it's not already so. Any more info can you point me to on this? >>> ISSUE #2: Should we set up a separate repository for the installer? > > I think we should consider how to best build the installer. The present MQ > based aproach is a little too difficult to use in my opinion. I would rather Same feeling here. > have a python script which could download the required components, and > combine all into an installer. If / when Mercurial gets Overlayed > repositories, we could also build a repository with all components that the > installer depents on. Of course, disk space / one-time network usage is not > a big problem these days, so we could use a repo even without the overlay > feature. We can't wait for Overlayed repo feature to realize soon enough. So we are going to redesign the layout for our short and long term use. > Maybe the forest extension can make building from a multi-repository > slightly easier. At least it provides cross-repo tags. Forest is new to me. I read the wiki page a bit, but it doesn't tell me much. What I really need a some case study to tell me what are the ways to utilize Forest. ------------------------------------------------------------------------- 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-develop mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/tortoisehg-develop
