At 10:54 14/03/01 +0000, you wrote:
>Mark Fowler <[EMAIL PROTECTED]> writes:
>
>> > <Finding out where perl is>
>Ooh, 'configure.cgi'.
>
>If only we could assume that they had a working perl on the box that
>they were installing from then we could write a cunning installer
>script which uploaded configure.cgi to the ISP and interrogated it via
>a LWP::... client to get a bunch of configuration stuff, which could
>then be used to generate a list of scripts that could run on the
>user's ISP, and which could then go on and upload the scripts.
Could we not produce something like configure.bat which is a hybrid shell
script/batch file that starts the configuration process by finding perl and
then launches perl to find out installed libraries.
Obviously it would produce lots of 'Command not found' messages etc but it
could quickly find perl (or not) and then move into a cleaner environment.
Matt
>
>Ooh... You don't even have to assume working perl on their box. You
>stick the interrogation stuff on the 'Not Matt's scripts' website. The
>punter then says "I want to run these scripts on such an ISP". NMS
>then checks to see if it has information about that ISP cached, and
>provides the appropriate scripts if so, or a copy of configure.cgi for
>the punter to upload. Once the punter has done the upload, he sets off
>an interrogation phase, which works out the capabilities of the
>particular user's environment and builds an appropriate script set.
>
>Hmm... it's just a simple matter of programming...
>
>--
>Piers
>
>
>
