The reason I'm asking is that the AS package dists for Windows has commented out the use of that script when running Installer.bat and instead do relocation directly in the script...
Perhaps this is just an artifact of the hen and the egg though...so assuming it's *otherwise* A Good Thing, what limitations am I looking at? Also, the Installer.bat seems to do more - updating ppm data etc (I don't care for the stuff of html docs, shortcuts etc etc etc). The background is that I'm struggling to have a situation where I can keep a selected Perl under CM control (from a prior conversation on this list), and on the fly, in the makefile, make sure it's valid for whatever location it happens to find itself in. This has so far proved to be a bit more troublesome than I had anticipated for lots of small reasons (for Win32. though I believe/hope it will be more straightforward in Unix...). Unpacking an AS package style zip and running the installer unattended seemed to be a good choice but is somewhat hampered by the Installer.bat not being possible to run unattended without hacking it, so I'm exploring other means... ken1 _______________________________________________ ActivePerl mailing list [email protected] To unsubscribe: http://listserv.ActiveState.com/mailman/mysubs
