Hello Gisle,
> I tried to recreate this, but that did not work out since when I invoked > the MSI to install the second "ActivePerl" on the system it just gives me > a menu that says: > > * Modify > * Rapair > * Remove > > which apparently would just do stuff with the installation I already > have. Did you use the MSI installer for the first perl as well? > Yes and no. :-) I originally installed Active Perl with the MSI installer in another workstation, and I did it on the D: unit, trying to keep the *nix-like path (/usr/bin/perl) to avoid certain problems running scripts on both Unix and Win32 platforms that required the shebang line. After writing a lot of modules and stuff, I was in charge of moving all that to a production server, so I first tried moving only the folder "/usr" to the QA server. Everything worked perfectly, so I added that folder to a first import in our repository, and later, we exported that folder from the repository to the production server. Ever since then, I work in the development server in conjunction with the repository and I just export the changes from the repository to the other servers. So, answering you question (sorry if I explained too much), this Perl installation was not made in this workstation by the MSI installer, I just "checked out" the "usr" folder from the repository. But it was, some time ago, originally installed in another computer with the MSI installer. Thanks again, Paco Zarabozo _______________________________________________ ActivePerl mailing list [email protected] To unsubscribe: http://listserv.ActiveState.com/mailman/mysubs
