Re: svn: /php/php-benchmarks/trunk/ benchweb/config.php benchweb/deploy.php benchweb/functions.php
benchweb/installers/phpbb/bench/LoremIpsum.class.php benchweb/installers/phpbb/bench/Post.php benchweb/installers/phpbb/bench/Record.php bench

On Fri, Aug 14, 2009 at 8:13 PM, Hannes Magnusson<bjori@php.net> wrote: > On Fri, Aug 14, 2009 at 18:04, Paul Biggar<paul.biggar@gmail.com> wrote: >> On Fri, Aug 14, 2009 at 4:37 PM, Hannes Magnusson<bjori@php.net> wrote: >>> On Fri, Aug 14, 2009 at 17:15, Paul Biggar<paul.biggar@gmail.com> wrote: >>>> Hi Pierre, >>>> >>>> On Fri, Aug 14, 2009 at 3:46 PM, Pierre Joye<pierre.php@gmail.com> wrote: >>>>> On Fri, Aug 14, 2009 at 3:20 PM, Paul Biggar<paul.biggar@gmail.com> >>>>> wrote: >>>>> >>>>>> We include complete GPL programs. We do not try to use GPL code in >>>>>> programs we write ourselves. >>>>> >>>>> The license itself is a pain >>>> >>>> How so? >>> >>> Lets not go into religious, or I think A is better then B, discussions here. >> >> I'm not advocating for or against the GPL. I'm just saying that >> benchmarks take work and are hard to come by. It would be simpler for >> us (people working on benchmarks) if some benchmarks were not banned >> because of their license. > > And the same thing applies to any other project. If the work has > already been made by someone it is very annoying that we cannot use > that work due to GPL restrictions. > It has nothing to do with benchmarking or anything. Its simply that we > need the code to not be GPL. No, it doesn't apply to any other project. Other projects either link via C code (PECL or extensions), or are designed to be include()d is larger projects (PEAR). PHP benchmarks are only ever going to be called like so: <?php start_timer(); php $benchmark.php end_timer(); ?> In particular, they are never going to be include()d. >>> If you want to dig into the archives and see the various reasonings >>> for that over the years, feel free. >> >> I looked through php-internals for the word GPL, and found some cases > > The "original decision" probably predates internals@, try php-dev@, > pear-dev@ also has thorough posts about this. Thanks for the pointers. I found quite a number of discussions in both php-dev and pear-dev. I read through as much as I could, and there is no case like this one. In fact, nothing really comes close, as they are all discussions on code which would be "linked" in somehow. There is nothing that remotely resembles "linking" here, which is not the case for any C code, or for PEAR. I may have missed something of course. I failed to find the "no GPL in CVS" decision, or the arguments that led to it, but every argument I've seen has been about the viral nature of linking to GPLed code. Thanks, Paul -- Paul Biggar paul.biggar@gmail.com