Olivier Hoareau wrote: >> I don't think that people are gonna like that kind of approach, having two >> binaries with one of them coming from custom source should raise some >> concerns and you won't like the prospects of maintaining PHP for older >> Debian/Ubuntu versions. > My users currently does not matter about this kind of problem, they want to > be able to download a binary, put it in a directory and use it in command > line, whatever it contains. > The features provided by the tool are not php-centric (not only at least), > so I can target teams that do not know anything of php and how it needs to > be installed. > >> This method of distribution [phar] targets users who can read documentation >> and >> understand what "depends on PHP 5.3" means. > Lots of users I target does not know differences between php 5.2 and php > 5.3, some of them don't know even that php 5.3 exists or what phar is. > For the others, it is a possible solution, but not allowing multiple php > version on same box and requiring that I maintain multiple package of the > application (I will have to, but the less package I have to maintain the > more time I will have to improve features).
For those Linux users with a package manager, installing your app depending on php5.3 would just upgrade their php from 5.2 to 5.3. If they don't know the difference between 5.2 and 5.3 they are also unlikely to notice that they got a newer version. That said, it is easy to install a separate php version side-by-side in a *nix system. When doing the ./configure step, add a --prefix=/prefix/path/ and all php files will be stored insde that dir (unless you're overriding it with other arguments such as sysconfdif). For windows, the php project already provides standalone executables which don't depend on being installed at a specific location. -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
