oliver <[EMAIL PROTECTED]> writes: > all i'm saying is, it isn't a nessecary to pollute a PC with perl, > just because the installer needs it.
Don't think of it as pollution; think of it as the ultimate upgrade for VBscript. It lets you write stuff for your logon scripts (or whatever) using an almost-sane language. OK, so not everyone sees it that way. I have no objection to patches, as long as the behavior is optional and the default is what we do now. > It's like having all these services running that I'll never use > anyway. Personally, I don't like that ; ). But it's not a service; the only resource it consumes is disk space. I bet you already never use 90% of the stuff on your disk. > Patches, well the first question would be, does perl even run from a > different directory. I have heard a while ago perl MUST be in > C:\perl. I doubt that perl uses registry settings, so that would be a > big plus, also I doubt they use any 'special' dll's So it _should_ be > possible. If I can find the answer to this question, as soon as I find > some time, I could supply patches : ) Go for it. But Perl does use the registry; it has to find its library files somehow. On Unix this is a hard-coded path. On Win32, it is in HKLM\SOFTWARE\ActiveState\ActivePerl\<version>. You might be able to get away with setting the PERL5LIB (or PERLLIB) environment variable to "Z:\perl" or whatever first. If you find yourself facing any non-trivial design choices, please air them for discussion here. Thanks! - Pat ------------------------------------------------------- The SF.Net email is sponsored by: Beat the post-holiday blues Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek. It's fun and FREE -- well, almost....http://www.thinkgeek.com/sfshirt _______________________________________________ unattended-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/unattended-devel
