> Is there any way of installing modules under
> Windows 2000 without having access to the
> command line.
Some modules monkey around during install.
You might be able to get non-privileged monkeying
around done somehow, by firing off the install
process as a cgi, for example. But that will still
leave the problem that that still won't be enough
for some modules. For those remaining modules
you'll need cooperation from the sysadmin of the
Windows box. Given that that is the case, you
might just as well try to get cooperation and go
that route, or, if you fail to get cooperation, give
up on being able to install modules on that box.
In more detail:
My comments are based on knowledge of cpan
rather than ActiveState's module system. I would
expect them to share some basic traits, discussed
below, so I've responded anyway.
I can see one way to install a module without command
line access. It is basically the one you have already
discovered. But it won't work for some modules.
As you have discovered, installing a perl module
is often as simple as putting it in the right directory
(one included in @INC). You can do this various
ways, with two being to use a directory that is
already found in @INC, and another being to add
another directory using the use lib pragma.
But there may well be more to it than that for a
given module. Indeed, some require you have
root or similar privileges and do some serious
monkeying around during install. It all depends.
hth.
