> > Yes; but apart from the Apache module case, the 'all in one > dir' setup is > > also valid for all uses, and far more simple. Is there a good > reason why > > we should advocate a more complex installation process simply to > > accommodate PHP run as an Apache module? > > Its actually the other way around. cli/cgi is exception to the > common case. > 'all in one dir' works for all cases. Don't forget there are a > lot of people > installing php under IIS and other web servers.
Following discussion on irc, we're now waiting for Canada to come online so that Frank can explain how he has his sapi installations working without using PATH.. (in which case Edin's right - but what do the majority of new users install? cgi or sapi?)
