>  Also if we have some *published* standards/schema then when we/others do 
>  make standalone installations we know what to steer clear of to avoid 
>  messing with the standard installation (like how many apps put the 
>  php.ini or my.cnf/mysql dll's in %WINDIR% and break other installations) 
>  , avoiding all of that would give php-gtk2 on win32 some stability.
>  
>  I just know that when designed by committee we will end up with c:/php5 
>  and c:/windows php.ini both of which (especially the latter) are bad 
>  news.. however this issue has popped up enough times already that 
>  perhaps its time to solve it ?

Right now the best (read doesn't mess up other php installs) way to do 
this is to put a php-cli.ini in the SAME DIRECTORY as your php.exe 
(php-win.exe) that you want to use - I've preached before about how PATH 
works on windows and why it's better to dump the dlls you want in the 
same directory as the executable to avoid dll hell - if we could get 
people to do this instead of dumping stuff in c:\ and c:\windows I'd be 
a happy camper

>  I dont think x-platform should come into this particular argument.. 
>  linux is a whole different kettle of fish with bigger issues of 
>  dependencies/versions etc.. then again package management is not my 
>  thang ;)

Linux has it's own way of doing things - I vote to let them ;)

The "official" way to manage packages in windows is using installers. 
MSI is the microsoft technology for it and there are cool advantages to 
using the format (command line installs, deployement tools) - however 
it's dependency management sucks...

-- 
PHP-GTK General Mailing List (http://gtk.php.net/)
To unsubscribe, visit: http://www.php.net/unsub.php