> > You are free to repackage PHP debs and make your package depend on Debian > PHP 5.3 or your PHP 5.3. >
OK > 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). I am not a lawyer. You can distribute installer which downloads PHP from > the net (windows.php.net or its mirrors). If you repackage PHP and > distribute PHP itself and your code in one bundle, your bundle license > must be compatible with PHP license. that's what any layman would think. > Don't mix incompatible licenses in one package. > It was not my intention to mix licenses, so I have to use last "PHP License", not a problem, no ? If small percentage of your targets use PHP 5.3, then your goal should be > to make your package compatible with older PHP version. If you have > deliberately coded with namespaces or other stuff from PHP 5.3, recheck > your coding manual. What is more important for you? Proving to yourself > that you can use complex language constructs in your code or reaching your > target users. > I already have PHP 5.2 compatible version of the tool, the PHP 5.3 is a complete rewrite making use of namespace (a lot) / __DIR__ (a few) / closure (a few) / phar (a few) In order to be able to maintain my tool I want to use PHP 5.3. As I said, this is not a commercial tool, I am distributing it freely, my purpose is not to waste my time to maintain differents version but to be able to target maximum of people that needs this kind of features (i.e. code generation, command line aliases, virtual tree layout, custom command writing in pure php, i18n, trace/logging, automatic db upgrade, unit testing, continuous integration bindings ...) The tool of Alec seems to be very interesting for my purpose, so I will investigate. I am so sorry that today there is not an official way of packaging a standalone php application for people that don't have php already installed on their box, it could contribute to enhance php promotion. Thank you ! oha > -- > Tomas > > > > -- > PHP Internals - PHP Runtime Development Mailing List > To unsubscribe, visit: http://www.php.net/unsub.php > >
