Jan Ehrhardt in php.pecl.dev (Thu, 20 Nov 2014 03:05:35 +0100): >Jakub Zelenka in php.pecl.dev (Wed, 19 Nov 2014 13:33:26 +0000): >>Forcing all PECL devs to use extra branch is not the right solution IMHO. >>The best solution would be give devs choice. For example if you don't have >>'phpng' branch then try to compile master. > >This was my idea too. Do not force a PECL dev to use an extra branch, >but if they do call the extra branch 'phpng'. That way the choice for >the right bracnch is scriptable.
To make this convention future-proof, it would be best to also allow a scheme where the master is targeted for phpng and a special branch is for php 5.x. Obvious name for the 5.x branch: phpog. Then you get something like this. Compiling for php7: use the phpng branch if it exists, otherwise master. Compiling for php5.x: use the phpog branch if exists, otherwise master. If you think this is a good idea, how can we go futher? Jan PS for Pierre: you expressed some concerns about extension development for phpng in earlier stages. Would this be a way to go? -- PECL development discussion Mailing List (http://pecl.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
