Hi Robin,
Kevin Ollivier wrote:
Hi Robin and all,
I'm preparing to release a wxPython 2.6 build of wxMozilla. I was preparing to create ANSI and Unicode packages, when the thought crossed my mind that some people might have both installed now. It also crossed my mind that the folders will no longer simply be named "wx" and "wxPython", so the installer needs to be able to detect the correct folder(s) and install into them. Before I write up some scripts to deal with this, I had a couple questions about what I should expect:
1) I assume all new wxPython builds will be of the form of "wx-<ver>- <port>-<unicode/ansi>"? That is, there won't be any (official) builds using the wx and wxPython root folders any longer?
Correct. Although it can still be built/installed the old way by third-parties using INSTALL_MULTIVERSION=0 with setup.py. A call to getExtraPath(addOpts=EP_ADD_OPTS) is used to make the path name if INSTALL_MULTIVERSION is true.
2) Will version always be <major>.<minor>? No 2.6.1, for example?
Right, the stable series will always be <major>.<minor>. The 3rd digit will be added in the unstable series.
And can we say that extensions will be compatible throughout the 2.6 release series?
I hope so.
Good, those were the answers I was hoping to hear. 
If any, the only "official" builds not using MULTIVERSION will probably be Linux distros, and if they want to go that route they can package wxMozilla themselves.
Oh, and Robin, I was looking at your InnoSetup scripts in distrib, and I noticed your code block starts with "program Setup;" but I can't seem to find reference to this in later versions of InnoSetup. What does it do?
I'm using the "My Inno Setup Extensions" version, which includes a built-in pascal interpreter. So that block contains snippets of code that are executed during the install process.
Has it been removed from newer versions?
I havn't kept track of Inno Setup development for quite a while, (probably 2 or 3 years by now!) so I'm not sure where things stand with this extension. I think that the last I heard it was planned to merge the intrepreter into the main Inno Setup tool. I guess it's time for me to get updated, or maybe jump to the Nullsoft installer now that it is scriptable. (Or wait for CrossPack! )
Yes, they have integrated the interpreter; there is now a "[Code]" section in the InnoSetup package format. (Though I kinda like the old "include file" approach.)
I'll post a first version of CrossPack in the next week as I think it's (more than) ready to get some more eyes on it, and I think the test now will be moving some software over to using it, so that we have some real world tests to expose all the little extras that need to be added. I need to get some pressure to get working on the Linux backends too, so this will help provide that. (They exist, but I'm too involved in the Mac/Win packages that I'm working on right now to focus on them.)
I need to think about some of the more complicated stuff, like how to add functions like checking if a file exists (i.e. a particular wxPython version folder in a way that they can be used cross-platform/cross-format, and in general ways to extend CrossPack to add new functionality like this. For this time around, though, I'll probably take the cheap route out and list the ANSI/UNICODE versions as separate components the user can choose to install. 
Thanks,
Kevin
···
On May 11, 2005, at 12:04 PM, Robin Dunn wrote:
--
Robin Dunn
Software Craftsman
http://wxPython.org Java give you jitters? Relax with wxPython!
---------------------------------------------------------------------
To unsubscribe, e-mail: wxPython-dev-unsubscribe@lists.wxwidgets.org
For additional commands, e-mail: wxPython-dev-help@lists.wxwidgets.org