|| at May 9, 2008 at 12:57 pm
On 5/8/2008 9:15 PM, Adam Kennedy wrote:
The Inno script stuff is not what is blocking the install to multiple
paths, I intentionally removed it.
The reason we can't install to multiple paths is that far too much of
the Perl installation bakes in a single explicit path and isn't flexible
enough to change that.
Allowing install to custom paths would require extensive rewriting of
paths post-installation, which seems too dangerous to me.
The Inno half of the problem is the easy bit, it's the Perl part is
Doing a string search in an installed image found "c:\vanilla" in lots
of places, but not in a huge number of files. The only one that I was
sure was binary was a2p.exe. (There is also a .pod file, that I'm not
sure about.) So I'd say for everything other than a2p, it could be
feasible to do post-install edits.
David Golden wrote:
Goodness, yes! All the Inno stuff has been a hack so far. Talk to
Adam Kennedy directly and see about getting commit rights to the
On Thu, May 8, 2008 at 2:01 PM, Duncan Murdoch wrote:
The current Vanilla Perl installer forces a particular install location.
I've got lots of experience with Inno Setup scripts; would the project be
interested in patches to allow the script to specify the install location?
I see on the project page that you're looking for an MSI installer; I don't